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

Improve documentation about the semantic of Immediate Services #1276

Open
activeeon-bot opened this issue Aug 18, 2014 · 0 comments
Open

Improve documentation about the semantic of Immediate Services #1276

activeeon-bot opened this issue Aug 18, 2014 · 0 comments

Comments

@activeeon-bot
Copy link

Original issue created by Laurent Pellegrino on 18, Aug 2014 at 15:12 PM - PALIGHT-67


It is not clearly explained inside the Javadoc (PAActiveObject.setImmediateService and org.objectweb.proactive.Body) and the ProActive documentation that using immediate services break the Proactive semantic on the caller side (i.e. even if the method has a return type declared as void or if the method returns a refiable object and does not throw an exception, any call is synchronous. In other words, all the calls performed on an active object with a method declared as IS are synchronous!).

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