Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1S3qRu-0004RM-Gn for bitcoin-development@lists.sourceforge.net; Sat, 03 Mar 2012 15:00:42 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1S3qRt-0007UQ-M1 for bitcoin-development@lists.sourceforge.net; Sat, 03 Mar 2012 15:00:42 +0000 Received: from ishibashi.localnet (fl-184-4-164-217.dhcp.embarqhsd.net [184.4.164.217]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 17FB7560539; Sat, 3 Mar 2012 15:00:36 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Sat, 3 Mar 2012 10:00:27 -0500 User-Agent: KMail/1.13.7 (Linux/3.2.2-gentoo; KDE/4.7.4; x86_64; ; ) References: <201202281706.22650.luke@dashjr.org> <4F52294C.8080409@justmoon.de> In-Reply-To: <4F52294C.8080409@justmoon.de> 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: <201203031000.28760.luke@dashjr.org> X-Spam-Score: -0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1S3qRt-0007UQ-M1 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 15:00:42 -0000 On Saturday, March 03, 2012 9:23:08 AM Stefan Thomas wrote: > From what I understand the BIP uses a polling model, e.g. a miner would > use getmemorypool to request new work from a pool in intervals. Would it > make sense to specify a version of the API supporting long polling? You mean explicitly mention the getwork longpoll protocol as part of the getmemorypool BIP? Probably a good idea. > For BitcoinJS specifically, since we also support JSON-RPC over TCP, I'd > even be interested in a genuine "push" API. Something like C->S > "listenmemorypool", S->C "updatememorypool" (continually). 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.