Hi Benjamin,
The EXACTLY ONCE INORDER delivery assurance is implemented in both client
and the server Endpoint Managers (EPM)
When the client sends the messages, he will keep on sending them until a
proper acknowledgement is received by him. But when the messages are
received by the Server EPM the messages are sorted according to the
wsrm:MessageNumber and duplicates are eliminated. So we have the above
delivery assurance.
The same scenario will happen when the Client EPM receive application
responses from the Server EPM.
Thanks,
Jaliya
----- Original Message -----
From: "Benjamin Schmeling" <[EMAIL PROTECTED]>
To: "Chamikara Jayalath" <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Tuesday, October 25, 2005 6:41 AM
Subject: Re: Call Semantics
Yes, thx.
How is this "Exactly Once" realized in sandesha?
In the ws reliable messaging specification I found nothing concrete, nor
any example, how it will be used in the protocol. Is it implemented
implicitly in the receiver and sender?
Is it planned to implement the other defined (ws-reliable messaging)
delivery assurances in near future?
Benjamin
Do u mean Delivery assurances.
If so Sandesha 1.0 support "In Order Exactly Once" delivery assurance.
Chamikara
On 10/25/05, *Benjamin Schmeling* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi All,
I am new to the list. Is it possible with sandesha to add call
semantics
to the message?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
