[prev in list] [next in list] [prev in thread] [next in thread] 

List:       olpc-devel
Subject:    Re: Avahi optimisations
From:       Jim Gettys <jg () laptop ! org>
Date:       2008-02-28 22:33:52
Message-ID: 1204238032.5759.3.camel () localhost
[Download RAW message or body]

OK, put like this, I agree with you.  We can burn 12 bytes to save a
flag day conversion; we will already have saved a ton of bytes as it is;
12 bytes is no more than a 10% improvement on top....
                                - Jim

On Thu, 2008-02-28 at 21:27 +0200, Morgan Collett wrote:
> Ivan Krstić wrote:
> > On Feb 26, 2008, at 5:48 AM, Morgan Collett wrote:
> >> actually we are normally using b64 encoding so
> >> that brought it down to 28 bytes. Using SHA-256 it's 44 bytes in the TXT
> >> record.
> > 
> > 
> > But _why_ are we encoding at all? TXT RDATA is one or more character
> > strings, which are each a length octet followed by up to 255 arbitrary
> > characters treated as a binary string. Am I misremembering the RFC?
> 
> I made this comment on #6572 but perhaps it's worth repeating here to a
> wider audience:
> 
> Not base64 encoding the "key" makes current builds fail to get the buddy
> properties due to a D-Bus issue that needs a workaround. This means you
> don't see any buddies in mesh view, although they can see you.
> 
> So if we stop base64 encoding, we lose interoperability with the
> existing builds and need a flag day to upgrade. This is to save 12 bytes.
> 
> Is that worth it?
> 
> 
> Morgan
> _______________________________________________
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
-- 
Jim Gettys
One Laptop Per Child


_______________________________________________
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

[prev in list] [next in list] [prev in thread] [next in thread]