It specifically states "Parsers may support base16 and base85."
Therefore the DTD must support this statement. Meadhbh S. Hamrick wrote:
this is because Marv updated the wiki to add base85 support, then sent a message out to this list claiming the llsd implementation does not match the documentation.base85 is NOT canonical.if you find an implementation that accepts base85, great! more power to you. but as far as OGP is concerned, we will currently barf on XML serializations that include base85. in other words... while you are free to generate messages that include base85 encodings, we are also free not to honor them. as neither the original LLSD wiki page (before Marv changed it) or the implementation used base85, it is not currently considered canonical.there's a process for getting things changed in OGP and in our existing non-OGP implementation. the process involves "consensus and working code." it does not involve changing the wiki to match a feature you want, then complaining that specifications and/or implementation don't match the wiki.i believe there was a discussion about base85 and the conclusion was that it buys you about a 7% savings over base64 which is minimal compared to the types of savings expected from just using a gzip transfer encoding.so i think the discussion went something like...if we're going to have to modify code, why would we want to modify code to add a 7% improvement when we could modify code to add an undefined, but expectedly higher value?-cheers -m/∞ On Sep 13, 2008, at 4:01 PM, Gareth Nelson wrote:As far as i'm aware, the sample python code and llcommon/llsd.cpp both totally lack this support. On Sat, Sep 13, 2008 at 9:52 PM, SignpostMarv Martin <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:The current LLSD spec (not the OGP drafts) mentions optional support for base16 & base85 support. Now, some of the peeps in AW Groupies hadn't even heard of base85 till Imentioned it yesterday- do any of LL's current services use either of theseoptional encodings ? ~ Marv. _______________________________________________ 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/SLDevPlease read the policies before posting to keep unmoderated posting privileges
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges
