Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow client code to tailor Kryo. #47

Open
sageserpent-open opened this issue Jul 2, 2018 · 0 comments
Open

Allow client code to tailor Kryo. #47

sageserpent-open opened this issue Jul 2, 2018 · 0 comments

Comments

@sageserpent-open
Copy link
Owner

There are several workarounds in the code for specific classes that tend to be referred to in client domain models. This will only get worse in future.

Let's all client code to register serializers (and possibly instantiation strategies) via callbacks or something else that doesn't fully expose with Plutonium does with Kryo, but allows some tailoring of the latter.

We need to be careful that fancy inter-item serialization in 'ItemStateStorage' plays well with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant