From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RchkO-0003DT-Fa for bitcoin-development@lists.sourceforge.net; Mon, 19 Dec 2011 18:15:36 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1RchkN-0001Er-BH for bitcoin-development@lists.sourceforge.net; Mon, 19 Dec 2011 18:15:36 +0000 Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net [184.4.160.40]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id AD639560505; Mon, 19 Dec 2011 18:15:29 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Mon, 19 Dec 2011 13:15:24 -0500 User-Agent: KMail/1.13.7 (Linux/3.1.4-gentoo; KDE/4.7.3; x86_64; ; ) References: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com> <201112191130.43721.luke@dashjr.org> <4EEF6EA2.4060709@parhelic.com> In-Reply-To: <4EEF6EA2.4060709@parhelic.com> X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112191315.25857.luke@dashjr.org> X-Spam-Score: -2.4 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -2.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RchkN-0001Er-BH Subject: Re: [Bitcoin-development] [BIP 15] Aliases X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2011 18:15:36 -0000 On Monday, December 19, 2011 12:04:34 PM Jordan Mack wrote: > I still think HTTPS should be used, at the minimum. Using HTTPS is > standard to every website out there that deals with financials, even if > it is not a perfect system. Why should Bitcoin adopt a more lax policy > than everyone else? Sure, I meant HTTP as the underlying protocol. TLS/SSL should of course be required in some form. > I thought that JSON support was fairly common these days. I personally > prefer XML in most cases, but since JSON is already used with the RPC, > it seemed like a natural fit here. JSON-RPC won't go on forever. In any case, bitcoind's use of JSON-RPC is exactly why I (and many other developers) have come to the realization how poorly supported JSON really is. Most of the common languages do have a library, but almost all of them have one issue or another (particularly around the very undefined Number type). XML shares the same binary-data problem as JSON, too. As slush mentioned, no additional serialization is necessary anyway. > Binary data can be base64 encoded, although I'm not sure why you would need > to send back binary in an alias response. Because computers work with binary. I don't think anyone wants to implement a fully functional script assembler just to send funds. > What exactly do you mean by "custom output script"? This suggests you need to learn more about how Bitcoin works ;) https://en.bitcoin.it/wiki/Script