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

serialization interface not required for quick prototyping on-node #9

Open
jjwilke opened this issue Mar 21, 2017 · 2 comments
Open

Comments

@jjwilke
Copy link
Contributor

jjwilke commented Mar 21, 2017

We should still require this by default, but there should be a way to turn off this requirement (via ifdefs or something created by configure) if I want to quickly implement something that doesn't require serialization functionality. On-node tasking only.

@dhollman
Copy link
Contributor

this is easy enough to change; the harder part is propagating that information piece-wise to the backend. I would need a few more methods on SerializationManager to tell the backend something isn't serializable (and I would need to propagate this information up to Task::is_migratable()). Still, shouldn't take long.

@jjwilke
Copy link
Contributor Author

jjwilke commented Mar 22, 2017 via email

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

3 participants