|
Unfortunately no. What you are asking for is essentially what we
already have - both old and
new viewers work because of a special coded server. We simply can not
maintain this state. The issue is our capabilities server used to run on a web service platform that had a bug in it, and our old viewers relied on this bug. We have since switched to using Apache as our platform for the capabilities server. To support older viewers we are currently running a slightly modified version of Apache to also have this bug. The modified Apache is a problem though - it makes keeping up to date difficult and complicates our future development. We must stop maintaining this modified version of Apache and to do that we must stop supporting these old viewers. - Kelly On 3/2/09 3:17 PM, Tigro Spottystripes wrote: would it be an option to have the servers talk differently based on the version of the client connecting to it? and would that help with the issues present now? (like, wouldn't this make it so newer version have to do it right while still allowing olders to do it wrong for a longer while? )Rob Lanphier escreveu:Hi folks, The current version of our server infrastructure for capabilities has a misfeature in it, where 500 responses have a stray colon in them. Capabilities are meant to be HTTP-compliant, but this stray colon is not. However, that incompatibility is required to maintain compatibility with 1.20.17 and earlier viewers (and their derivatives). Maintaining this situation is a pain, because coercing standards-based infrastructure (like Apache) to do the wrong thing is a major pain. We eventually would like to eliminate this aberration from our infrastructure, but that would mean that older viewers would stop working. We'll give you plenty of warning before actually changing this infrastructure, but we figured it's best to get the technical information out now so that this will hopefully be a moot point by the time we announce a timeline. We're asking that everyone who has a viewer based on 1.20.17 and older to either upgrade to a newer base revision of the viewer (e.g. 1.21 or later) or apply a fix as described here: https://wiki.secondlife.com/wiki/Deprecated_Protocol_Features#Deprecated_protocol_feature:__stray_colon_in_HTTP_500_responses_.28viewers_1.20.17_and_earlier.29 ...with patches attached here: https://jira.secondlife.com/browse/VWR-12248 Thanks! Rob _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges |
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges
