Hey Baron, Is that the session ID of the connection or could it be a virtual session ID for example from the PHP session_id() functio)? For a lot of purposes (analytics as well as session consistency) what counts is the user session, not the database connection.
Cheers, Robert On 4/30/09 8:05 PM PDT, "Baron Schwartz" <[email protected]> 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? _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
