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

synchronization model #153

Open
Rieprecht opened this issue Jan 28, 2016 · 2 comments
Open

synchronization model #153

Rieprecht opened this issue Jan 28, 2016 · 2 comments

Comments

@Rieprecht
Copy link
Contributor

Decide upon synchronization inside the backend (should jobgraph and components be synchronized)
@citmp2015/all
Please contribute to this discussion. Can we trust the backend controller to not reuse references?

@adrianbartnik
Copy link
Contributor

Can you clarify what you mean by synchronized? As far as I understand, a jobgraph consist of components.
And by "reuse references", do you mean modifying single components after a jobgraph has been created? I think you can make that assumption.

@Rieprecht
Copy link
Contributor Author

The issue is realted to all objects, that are shared alone with a JobGraph objects. For the JobGraph and components themselves, this may include methods like init(), setParameters, getParameter, getParameterMap(), setParameterSet, ...
Since each component and the graph itselve contains multiple maps (hashmap) it maybe useful to use synchronized or immutable maps from the apache collections module to avoid asynchronous manipulation/access exceptions from DAU's

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

2 participants