[
https://issues.apache.org/jira/browse/SANDESHA2-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Murray updated SANDESHA2-107:
----------------------------------
Attachment: thinclient.patch
This patch attempts to send the create sequence on the application thread and
waits for the http timeout. When the call returns the sequence is either
established or the base http timeout has been reached.
> Blocking the application client till the sequence is established
> ----------------------------------------------------------------
>
> Key: SANDESHA2-107
> URL: https://issues.apache.org/jira/browse/SANDESHA2-107
> Project: Sandesha2
> Issue Type: New Feature
> Reporter: Chamikara Jayalath
> Attachments: thinclient.patch
>
>
> It may be desirable if the users can get to know weather the sequence
> creation was established before the first message invocation call is
> returned. This may be even true in the fireAndForget scenario. So by default
> we will try to get the CreateSeqence exchange completed before returning to
> the user. If something goes wrong we can inform the user immediately.
> If there is an associated user level transaction things will be different. In
> this case we will not be able to stay blocked since the sender will not have
> resources to send the message till user transaction is committed. So we will
> be always returning to the user.
> This was also discussed at the Hackathon. User and developer comments are
> more than welcome.
--
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]
