OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [ws-rx] MessagePending


Anish

Only if the RM layer is aware of the MEP. Of course some implementations 
might not be (or might be built into a gateway and therefore unable to 
know).

Paul   

Anish Karmarkar wrote:
> Paul Fremantle wrote:
>> Rereading the spec around MakeConnection, I realize that we defined 
>> MessagePending as only applicable on a message flowing back on a 
>> MakeConnection backchannel. It seems to me that we could usefully add 
>> this message in cases where a response is flowing on a back channel.
>>
>> For example. Suppose I have an interaction
>>
>> 1. GET1 ----->
>> <---- RESPONSE1
>>
>> 2. GET2----->
>> (response lost)
>>
>> 3. GET3----->
>> <------RESPONSE3
>>
>> In 3, the Get will have an ack for response1, and the server can 
>> indicate that response 2 is missing.
>>
>
> When the RMD (client) gets RESPONSE3, given that the messages have 
> sequence number, won't the RMD automatically know that there is a 
> pending RESSPONSE2 which it hasn't received yet?
>
> -Anish
> -- 
>
>> We already have logic to decide when piggybacking of acks is 
>> appropriate. I believe the logic could be extended to decide when it 
>> was ok to send back a MessagePending header:
>>
>> * In the sequenceID case, it would be appropriate whenever the 
>> message being sent back was part of the same Offered response sequence.
>> * In the URI case, it would be appropriate whenever the replyTo URI 
>> matched the MessagePending URI.
>>
>> Paul
>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]