If alias resolution was guaranteed to always be just the address, then yes, I would opt for no serialization at all. A simple plain text response of an address is about as simple as it can get.
There are already a lot of good ideas floating around about how the alias protocol could be extended. Is it really going to stay that simple for long? I would personally much just have a serialized response upfront, rather than having to worry about backward compatibility in the future. On 12/19/2011 10:17 AM, slush wrote: > In my opinion, there's not necessary any payload format (json, xml, > multipart). In keeping stuff KISS, everything we need is just an address > in response + potentially some stuff like HTTP redirects (for providing > additional compatibility for proposal of bitcoin URIs with "amount", > "label" and other parts). I don't see reason why we need some extra > payload yet. ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
