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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RciKf-0004b6-LI for bitcoin-development@lists.sourceforge.net; Mon, 19 Dec 2011 18:53:05 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.175 as permitted sender) client-ip=209.85.213.175; envelope-from=jordanmack1981@gmail.com; helo=mail-yx0-f175.google.com; Received: from mail-yx0-f175.google.com ([209.85.213.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1RciKe-0002aH-Tt for bitcoin-development@lists.sourceforge.net; Mon, 19 Dec 2011 18:53:05 +0000 Received: by yenm12 with SMTP id m12so3895823yen.34 for ; Mon, 19 Dec 2011 10:52:59 -0800 (PST) Received: by 10.236.191.5 with SMTP id f5mr29945456yhn.122.1324320779499; Mon, 19 Dec 2011 10:52:59 -0800 (PST) Received: from [192.168.0.50] (c-67-188-239-72.hsd1.ca.comcast.net. [67.188.239.72]) by mx.google.com with ESMTPS id u47sm31403984yhl.0.2011.12.19.10.52.58 (version=SSLv3 cipher=OTHER); Mon, 19 Dec 2011 10:52:58 -0800 (PST) Sender: Jordan Mack Message-ID: <4EEF8806.6070707@parhelic.com> Date: Mon, 19 Dec 2011 10:52:54 -0800 From: Jordan Mack User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com> <201112191130.43721.luke@dashjr.org> <4EEF6EA2.4060709@parhelic.com> <201112191315.25857.luke@dashjr.org> In-Reply-To: <201112191315.25857.luke@dashjr.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.4 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (jordanmack1981[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (jordanmack1981[at]gmail.com) 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RciKe-0002aH-Tt 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:53:05 -0000 I believe I'm missing something here. I was under the interpretation that alias resolution was going the KISS route, of basically a single HTTP request and response. How do you see binary data fitting into this? I'm not going to pretend that I know all the details of the difficulties that were encountered with JSON-RPC. But in the argument of developer accessibility, it still serves a purpose. If JSON-RPC support is removed, you will immediately lose a large pool of high level language developers. I would hope that support would not be dropped, even if it only remains as a secondary protocol with limited capability. Most high level developers are only going to use it for basic functions anyhow. On 12/19/2011 10:15 AM, Luke-Jr wrote: > Because computers work with binary. I don't think anyone wants to implement a > fully functional script assembler just to send funds. > > 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).