You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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
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?
The text was updated successfully, but these errors were encountered: