This thread has been "interesting" to follow.  But I considered it
completely "blue sky".

Are you guys supporting a change to the MySQL wire protocol?  Are
you guys supporting a change to _all_ API's that currently use
MySQL that would then have to stick somewhere all these "nice"
things in the exchange connection handshake?  What is the "idea"
of the "user agent" in this case?  I suppose what is meant is
that the thinking is that this "comment" field in the wire protocol
would be loaded up with whatever the API wanted.

On a typical web site running Apache/PHP/MySQL, the sequence would
have to be, I think:

        1.  PHP gets the "user agent"
        2.  PHP passes the arg to the connection request
        3.  This "user agent" sticks in the data in the
                wire protocol.
        4.  MySQL sticks this "user agent" into a (new)
                datastructure somewhere associated with
                the connection.
        5.  A (new) API call to MySQL can fetch this
                information

What am I missing here?

It seems to me that "all" you are asking for is

        1.  Change in the wire protocol
        2.  Design change in the MySQL API
        3.  Upgrade of all applications using the API
                in the world
        4.  Depending on all programs to stick data in
                this requested "comment" field in the
                same consistent manner, unless you are
                asking for more riders/piggybacks and more fields
                in the wire protocol such as "user agent".

Again, what am I missing here?  I don't see this as a
so-called "trivial" thingy.  It maybe could be done in
one local place (as first requested), but this isn't
trivial, and has no trivial impact, if it is to be
used generally.

_jef
----------------


Ansgar Becker wrote:
> 
> >   The  only  thing I would like is to be able to attach a comment to a
> >   connection  id  which  could be returned by the "mysqladmin process"
> >   command.  And  something  that  would not add more load to Mysql nor
> >   more coding in the client.
> 
> Yes!! Great idea. This would be helpful for hosters with many
> client-connectors to identify them. It could contain for example the name of
> the client-application ("useragent"), client-OS and some version-info. i
> think 100 chars will do.
> 
> Greetings, Ansgar
> http://www.mysqlfront.de/
> 
> ---------------------------------------------------------------------
> Before posting, please check:
>    http://www.mysql.com/manual.php   (the manual)
>    http://lists.mysql.com/           (the list archive)
> 
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

-- 
Justin Farnsworth
Eye Integrated Communications
321 South Evans - Suite 203
Greenville, NC 27858 | Tel: (252) 353-0722

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to