You could make use of the sequenceId to let the client and server know what message they are dealing with. Seems like no implementation make use of it. Some Facebooker care to explain what this legacy field was meant for?
On Fri, Sep 5, 2008 at 12:57 PM, Johan Stuyts <[EMAIL PROTECTED]> wrote: > Hi, > > What are the semantics for multiple asynchronous calls over the same > connection? Is a server allowed to process those out of order, or would most > clients expect previous requests to have been processed before new requests > are handled? > > Note that the use of a connection pool on the client side could cause the > requests to be processed out of order anyway. > > -- > Kind regards, > > Johan Stuyts >
