From: Stefan Thomas <moon@justmoon.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] getmemorypool BIP process
Date: Sat, 03 Mar 2012 15:23:08 +0100 [thread overview]
Message-ID: <4F52294C.8080409@justmoon.de> (raw)
In-Reply-To: <201202281706.22650.luke@dashjr.org>
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
>
next prev parent reply other threads:[~2012-03-03 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 22:06 [Bitcoin-development] getmemorypool BIP process Luke-Jr
2012-03-03 14:23 ` Stefan Thomas [this message]
2012-03-03 15:00 ` Luke-Jr
2012-03-03 17:08 ` Michael Grønager
2012-03-04 0:18 ` Stefan Thomas
2012-03-03 23:51 ` Geir Harald Hansen
2012-03-04 1:04 ` Luke-Jr
2012-03-04 17:49 ` Geir Harald Hansen
2012-03-03 15:44 Luke-Jr
2012-03-04 0:18 ` Stefan Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F52294C.8080409@justmoon.de \
--to=moon@justmoon.de \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox