I'm pretty sure all of the current implementations (with the possible exception of Erlang) will processes them in order. I'm not sure whether we should make this a defined behavior, but I'm leaning toward "no".
--David Johan Stuyts 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 >
