Me & John were discussing a 'update' server hosted in the gna.org
project webspace. Something that has a copy of the latest keywords.txt,
protocol.txt and what version SL likes you to login as.
The idea would be:
libsl sends it's version and it's protocl.txt/keyword.txt checksum to
--> http://home.gna.org/libsecondlife/update.php
Which either returns a:
* 'clear to go' signal - your client is fully compatible, and can login.
* 'update' signal, offering URL's to the latest keywords/protocl.txt,
and the current SL version number
* 'need new libsl' signal - where the version of libsl listed is
completely incompatible with SL, and cannot be upgraded, save a DLL update.
-Adam
John Hurliman wrote:
Tom Wilson wrote:
does libSL check server version numbers on login?
by keeping the libSL DLL in sync with the servers, we would get around
the upload fee problem.
It doesn't right now, but should. Before login you are supposed to
contact a server (not sure exactly how this works, it's in any snowcrash
dump though) and send a packet with the MD5 of your protocol file (not
sure if it's of the encrypted or decrypted one). The server lets you
know if there is a new version of the protocol file available. We could
also revert back to using the actual version number of the latest
current release during login, but this turned out to be a big pain every
time LL released a required update that didn't affect the protocol or
keywords file.
John
_______________________________________________
libsecondlife-dev mailing list
libsecondlife-dev@gna.org
https://mail.gna.org/listinfo/libsecondlife-dev
_______________________________________________
libsecondlife-dev mailing list
libsecondlife-dev@gna.org
https://mail.gna.org/listinfo/libsecondlife-dev
