Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1S3sih-0000Vf-Lu for bitcoin-development@lists.sourceforge.net; Sat, 03 Mar 2012 17:26:11 +0000 Received-SPF: softfail (sog-mx-3.v43.ch3.sourceforge.com: transitioning domain of mac.com does not designate 95.166.54.49 as permitted sender) client-ip=95.166.54.49; envelope-from=gronager@mac.com; helo=mail.ceptacle.com; Received: from 2508ds5-oebr.0.fullrate.dk ([95.166.54.49] helo=mail.ceptacle.com) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1S3sig-0003eH-Jk for bitcoin-development@lists.sourceforge.net; Sat, 03 Mar 2012 17:26:11 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.ceptacle.com (Postfix) with ESMTP id 65C2F1836229; Sat, 3 Mar 2012 18:08:58 +0100 (CET) X-Virus-Scanned: amavisd-new at ceptacle.com Received: from mail.ceptacle.com ([127.0.0.1]) by localhost (server.ceptacle.private [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yn-34WK4-hrc; Sat, 3 Mar 2012 18:08:58 +0100 (CET) Received: from [10.0.1.28] (2508ds5-oebr.0.fullrate.dk [95.166.54.49]) by mail.ceptacle.com (Postfix) with ESMTPSA id 3AAB31836223; Sat, 3 Mar 2012 18:08:58 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=us-ascii From: =?iso-8859-1?Q?Michael_Gr=F8nager?= In-Reply-To: <201203031000.28760.luke@dashjr.org> Date: Sat, 3 Mar 2012 18:08:57 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <345337E5-9645-40B7-9A77-F65DD1694CEA@mac.com> References: <201202281706.22650.luke@dashjr.org> <4F52294C.8080409@justmoon.de> <201203031000.28760.luke@dashjr.org> To: Luke-Jr X-Mailer: Apple Mail (2.1257) X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gronager[at]mac.com) 1.0 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail) X-Headers-End: 1S3sig-0003eH-Jk Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] getmemorypool BIP process 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: Sat, 03 Mar 2012 17:26:11 -0000 >=20 > HTTP and JSON-RPC are a client-server model; there is no way for the = server to=20 > make calls to the client. It's not practical to expect clients to run = their=20 > own JSON-RPC server - many cannot listen on WAN ports at all. Well, I think what Stefan had in mind was http keep-alive combined with = an event system. So similar to the way a web chat application work, just = for json-rpc. BitcoinJS already uses this for realtime updating a = webwallet. Libcoin is also prepared for this with a quite advanced, = non-blocking, http server so I second Stefan that an update function = could indeed be of relevance. Btw - question to Stefan as the JavaScript guru - what do you consider = the standard/defacto-standard/right/best-practice way of doing S->C = json-rpc, what (javascript) library do you use for this? Cheers, Michael >=20 > = --------------------------------------------------------------------------= ---- > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing=20 > 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