Yeah, this is something we originally scoped in so that we'd be able to support multi-plexing, or asynchronous request processing (i.e. returning results in a different order than the requests).
However, we never fully got around to actualy implementing said functionality, so today the sequence numbers are all but ignored, and not even properly incremented in some of the languages. >> It seems that each time a Client sends a message, it attaches a sequence id, but in both languages I looked at (ruby and java), the sequence id is never changed on send (so it's always 0), and it's completely ignored on receive. Is there any purpose at all to this sequence id? -Kevin Ballard -- Kevin Ballard [EMAIL PROTECTED]
