summaryrefslogtreecommitdiff
path: root/32/c2e0971bbf22be115af36d6a60e55b2570a795
blob: 3226db86a77637aa3ff4cfdad1d369f94148f9e7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <moon@justmoon.de>) id 1S3prm-0004Ru-D9
	for bitcoin-development@lists.sourceforge.net;
	Sat, 03 Mar 2012 14:23:22 +0000
X-ACL-Warn: 
Received: from sulfur.webpack.hosteurope.de ([217.115.142.104])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1S3prk-0000k2-8d for bitcoin-development@lists.sourceforge.net;
	Sat, 03 Mar 2012 14:23:22 +0000
Received: from 84-73-121-121.dclient.hispeed.ch ([84.73.121.121]
	helo=[192.168.0.21]); authenticated
	by sulfur.webpack.hosteurope.de running ExIM with esmtpsa
	(TLSv1:AES256-SHA:256)
	id 1S3pre-0007wd-6H; Sat, 03 Mar 2012 15:23:14 +0100
Message-ID: <4F52294C.8080409@justmoon.de>
Date: Sat, 03 Mar 2012 15:23:08 +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: <201202281706.22650.luke@dashjr.org>
In-Reply-To: <201202281706.22650.luke@dashjr.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-bounce-key: webpack.hosteurope.de;moon@justmoon.de;1330784600;351c820f;
X-Spam-Score: 0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	0.5 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1S3prk-0000k2-8d
Subject: Re: [Bitcoin-development] getmemorypool BIP process
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 14:23:22 -0000

 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?

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

On 2/28/2012 11:06 PM, Luke-Jr wrote:
> Please review and comment/critique:
>      https://en.bitcoin.it/wiki/BIP_DRAFT:_getmemorypool
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>