On Thu, 17 Jan 2008, nash wrote: > Hello, > I've thought of this before, and Lee indirectly mentioned it earlier > when he talked about tpai possibly being stupid, or other clients with > broken filter implementations. > > Currently the client ID is essentially a free form string. All bad. > Servers can't get anything out of it in a sane consistent manner. > > Should we: > - Leave it > - Add a few extra fields to the connect message indicating the client, > and version > - Require (or strongly suggest) TP04 clients include particular > metadata in the string > > The last is my preferred suggestion, something like: > "[" Vendor Name "/" Client Name "/" Version "/" Build Info "]" > > So: > [Debian/Galaxie/0.0.3-rc3/221] > [-/tpclient-py,tpproto-py/1.2/e45a3c4] > [Kubuntu/Parsek/4.0rc3/[EMAIL PROTECTED] > > I'm sure someone can suggest a better way of doing it... > > Thoughts suggestions etc? > > Regards, > nash
What libtppro-{py|cpp} do currently is:
libraryname/version clientname/version
So:
libtpproto-cpp/0.1.2 tpclient-cpptext/0.0.1
and
libtpproto-py/0.2.2 libtpclient-py/0.2.99 tpclient-pywx/0.2.99
for example.
This follows (somewhat) what HTTP Use-Agent: strings are.
I would be open to other suggestions, other than it could be good to include a
bit more data and to actually spec it.
Later
Lee
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
