[
https://issues.apache.org/jira/browse/SANDESHA2-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gatford resolved SANDESHA2-108.
--------------------------------------
Resolution: Fixed
Resolved in revision 592342
> Invoker thread should be avoided in ordered invocation whenever approapriate
> ----------------------------------------------------------------------------
>
> Key: SANDESHA2-108
> URL: https://issues.apache.org/jira/browse/SANDESHA2-108
> Project: Sandesha2
> Issue Type: Improvement
> Reporter: Chamikara Jayalath
>
> Always having a thread switch at the invoker seems to be a performance hit.
> We can change this to a model where we allow the current thread to proceed
> as long as the message is the next message to be invoked.
> To make this work correctly we need a new feature from Axis2. We need to know
> when the invocation of a certain message get completed in order to allow the
> next message to proceed. Currently we cannot do this for OneWay scenarios.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
