JF> I don't know why I got interested in this thread...
More important (or less), why are you so negative ?
JF> I suppose you don't need a change to the wire protocol if
JF> you have, logically, something like below. The API has
JF> to be changed, however.
JF> id = do_a_connedtion(arg)
JF> set_comment_on_connection(id, "this_is_my_comment")
JF> // later
JF> some_array = get_connection_comments()
JF> // parse the array comments
JF> // do something or other as function of comment
Not even have to modify the API. Read my previous email.
JF> Question: Why, again, do you want this? You must see some utility
JF> in this other than academic interest, or taking statistics, or
JF> mischief, such as munging some field returning data to a Windows
JF> client with "Screw Bill Gates" prepended to his blob requests, or
JF> kicking off connections to, say, any client in Tana Tuva.
I see an interest has an administrator of a really big site with 10
Mysql servers each answering more than 1000 queries each seconds.
Queries that could come from hundreds of dynamic web pages, scripts,
cronjobs, applications ...
When something goes wrong, this feature would really help to debug
and to fine a lot more quickly where the problems comes from.
JF> For readers like me, sitting on the sidelines, the "need" for this
JF> facility is obscure. Please make your case more evident.
Hope this is more clear to you now.