> 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 > ------------------------------------------------------------------------------ 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