On 1 May 2009, at 04:05, Baron Schwartz wrote:
Suggestion: consider including the session ID in every packet back and forth to the server. Reason: it makes it much easier to do things with the traffic. Consider my use case -- observing traffic. If I haven't been watching since the beginning, I don't know what session ID I'm looking at. Other use cases might exist, such as the ability to join an existing session, and thereby have multiple connections sharing a transaction. Or just debugging. Drawback: an extra 4 bytes per packet?
Having the global transaction id on the wire could be pretty helpful too. :)
Cheers, Mark -- Mark Leith MySQL Regional Support Manager, Americas Sun Microsystems, Inc., http://www.sun.com/mysql/
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
