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

Force the programmer in some way to only send immutable objects over ports #41

Open
wilcowijbrandi opened this issue Jul 13, 2015 · 0 comments

Comments

@wilcowijbrandi
Copy link
Member

A very common pitfall is that the programmer sends a data object over a port which is not really a data object.

In one case, the programmer was sending the same state object over a port and kept changing the internals of the object. This works fine in some cases, but can lead to really difficult to solve problems later on.

One way to solve this could be by only allowing serializable objects and serializing/deserializing them in the connection.

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

No branches or pull requests

1 participant