Message-ID: <4F52B4C9.3060900@justmoon.de>
Date: Sun, 04 Mar 2012 01:18:17 +0100
From: Stefan Thomas <moon@justmoon.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <201203031044.17005.luke@dashjr.org>
In-Reply-To: <201203031044.17005.luke@dashjr.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Bitcoin-development] getmemorypool BIP process
Precedence: list

> I've updated the draft to include long polling, and remove some assumptions of
> using HTTP for transport.

Looks good to me.

On 3/3/2012 4:44 PM, Luke-Jr wrote:
> On Saturday, March 03, 2012 10:05:58 AM Gavin Andresen wrote:
>>> HTTP and JSON-RPC are a client-server model; there is no way for the
>>> server to make calls to the client. It's not practical to expect clients
>>> to run their own JSON-RPC server - many cannot listen on WAN ports at
>>> all.
>> You're doing that thing where either you say something before you've
>> done adequate research, or you're being needlessly pedantic; I just
>> copied and pasted this from section 2.1 of the JSON-RPC spec:
> I wasn't aware anyone was considering JSON-RPC over anything other than HTTP.
>
> I've updated the draft to include long polling, and remove some assumptions of
> using HTTP for transport.
>
> ------------------------------------------------------------------------------
> Virtualization&  Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>