You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Benjamin Schmeling <Be...@gmx.de> on 2005/11/01 15:52:20 UTC
Re: Call Semantics
Thanks,
but what is with the other delivery assurances? Do you think they are
provided implicitly by exactly once or why are they not being
implemented separately so the user can choose between them?
Benjamin
> 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"
> <Be...@gmx.de>
> To: "Chamikara Jayalath" <ch...@gmail.com>
> Cc: <sa...@ws.apache.org>
> 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* <Benjamin_Schmeling@gmx.de
>>> <ma...@gmx.de>> 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: sandesha-dev-unsubscribe@ws.apache.org
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>> <ma...@ws.apache.org>
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Call Semantics
Posted by Jaliya Ekanayake <ja...@opensource.lk>.
Hi Benjamin,
They are not provided implicitly by exactly once delivery assurance. In the
current version of Sandesha support only exactly once delivery assurance and
the others are not implemented. It is not hard at all and easy. It is only
an implementation task and let's put them into 1.1 release. :)
Sandesha2 comes with all configurable delivery assurance.
Thanks,
Jaliya
----- Original Message -----
From: "Benjamin Schmeling" <Be...@gmx.de>
To: "Jaliya Ekanayake" <ja...@opensource.lk>
Cc: "Chamikara Jayalath" <ch...@gmail.com>;
<sa...@ws.apache.org>
Sent: Tuesday, November 01, 2005 9:52 AM
Subject: Re: Call Semantics
> Thanks,
>
> but what is with the other delivery assurances? Do you think they are
> provided implicitly by exactly once or why are they not being implemented
> separately so the user can choose between them?
>
> Benjamin
>
>> 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"
>> <Be...@gmx.de>
>> To: "Chamikara Jayalath" <ch...@gmail.com>
>> Cc: <sa...@ws.apache.org>
>> 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* <Benjamin_Schmeling@gmx.de
>>>> <ma...@gmx.de>> 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: sandesha-dev-unsubscribe@ws.apache.org
>>>> <ma...@ws.apache.org>
>>>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>>> <ma...@ws.apache.org>
>>>>
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>>
>>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Call Semantics
Posted by Jaliya Ekanayake <ja...@opensource.lk>.
Hi Benjamin,
They are not provided implicitly by exactly once delivery assurance. In the
current version of Sandesha support only exactly once delivery assurance and
the others are not implemented. It is not hard at all and easy. It is only
an implementation task and let's put them into 1.1 release. :)
Sandesha2 comes with all configurable delivery assurance.
Thanks,
Jaliya
----- Original Message -----
From: "Benjamin Schmeling" <Be...@gmx.de>
To: "Jaliya Ekanayake" <ja...@opensource.lk>
Cc: "Chamikara Jayalath" <ch...@gmail.com>;
<sa...@ws.apache.org>
Sent: Tuesday, November 01, 2005 9:52 AM
Subject: Re: Call Semantics
> Thanks,
>
> but what is with the other delivery assurances? Do you think they are
> provided implicitly by exactly once or why are they not being implemented
> separately so the user can choose between them?
>
> Benjamin
>
>> 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"
>> <Be...@gmx.de>
>> To: "Chamikara Jayalath" <ch...@gmail.com>
>> Cc: <sa...@ws.apache.org>
>> 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* <Benjamin_Schmeling@gmx.de
>>>> <ma...@gmx.de>> 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: sandesha-dev-unsubscribe@ws.apache.org
>>>> <ma...@ws.apache.org>
>>>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>>> <ma...@ws.apache.org>
>>>>
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>>
>>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org