[sldev] Unable to login with third party clients
Ryan Williams
rdw at lindenlab.com
Wed Apr 25 15:15:21 PDT 2007
John Hurliman wrote:
> josh at lindenlab.com wrote:
>>
>> As previously mentioned, the protocol has changed - release-candidate
>> after 1.14.1.2 will only connect to Aditi until the next Agni update. The
>> connection handshake has changed slightly as well - we now require
>> specific version numbers if they come from a known "channel" so we can
>> suggest/require upgrades. Specifying an different channel (e.g. "My Own
>> Viewer" instead of "Second Life Release", which is the default) will (I
>> believe) bypass the checks.
>>
>
> Now that the new grid is rolled out and libsecondlife clients (that
> aren't faking the version number) are locked out, can we get details on
> how you specify a different channel? An example of the XML in the login
> exchange, or a pseudo-XML hierarchy of what it looks like would be very
> helpful.
>
> Thank you in advance,
Here's the quickie reply -- I will put this up on the wiki in more
expanded form when I get more time.
When you login, you send an xml-rpc request to login.cgi, which contains
a bunch of parameters, including the version number in the form of
major/minor/patch/build. We have added a new parameter called "channel"
which is an arbitrary string. Also, we have compacted the four version
number parameters into a single string version.
Thus, the xml fragment would now be something like:
<member>
<name>channel</name>
<value>libsecondlife</value>
</member>
<member>
<name>version</name>
<value>1.15.0.2</value>
</member>
If we don't have an entry for the channel or version that you're
connecting with, it allows you to log in. If you're logging in with the
major/minor/patch/build specified individually, then it has to match
our existing versions (i.e. 1.15.0.2 -- this is how we're forcing all
old clients to upgrade). So, just change to sending the version as a
string and it should let you in.
-RYaN
> John Hurliman
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
More information about the SLDev
mailing list