|
4.0 Session
< Previous Next >
re: Resend Request
Scott Atwell / American Century <>
3 Jun 1998 11:32AM ETPlease refer to the table "Response by Message Type" within the "Message Recovery" section of the spec. There are certain messages, ResendRequest, included which should be "processed" before sending a ResendRequest.
> I am posting this here because there is almost no difference between the session protocols for 4.0 and 4.1.
>
> The spec. says on pg.15: "Note: it is imperative that the receiving application process messages in sequence order, e.g. if message number 7 is missed and 8-9 received, the application should ignore 8 and 9 and ask for a resend of 7-9."
>
> Suppose both parties are missing the top 3-4 messages. They both issue resend requests but since they have gap, they ignore the others resend request and keep sending their own resend requests.
>
> Is there anything in the protocol which would prevent from such a dead-lock or the wording should be changed so that only business messages are to be ignored and admin messages (or only ResendRequest) should be processed regardless of any gaps.
>
> Val
>
Resend Request Valentin Melamed / Ease Technologies, Inc. 3 Jun 1998 11:10AM ET re: Resend Request Ryan Pierce / Townsend Analytics Ltd. / Archipelago LLC 5 Jun 1998 4:43PM ET re: Resend Request
Scott Atwell / American Century 3 Jun 1998 11:32AM ET
|
