rich1.0npub1ad7209g90jnu400x74quws0xv8gpxs2fxnjexnpwqnrxwa39exdq5gl2p6https://nostr.ae/npub1ad7209g90jnu400x74quws0xv8gpxs2fxnjexnpwqnrxwa39exdq5gl2p6njumphttps://nostr.ae📅 Original date posted:2011-12-19 🗒️ Summary of this message: Slush suggests that there is no need for a payload format like JSON or XML, and all that is required is an address in response. 📝 Original message: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. slush On Mon, Dec 19, 2011 at 7:13 PM, Jordan Mack <jordanmack at parhelic.com>wrote: > If the idea is to "KISS", and provide a method that is both quick and > easy to implement for the average developer, then JSON is a stand out > option. Using HTTP for the data interchange will make things difficult > for a lot of developers if multipart responses are used. JSON will be > greeted with open arms. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111219/33ea8eb3/attachment.html>