From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Useful bitcoin patches...
Date: Fri, 01 Jul 2011 18:25:27 +0200 [thread overview]
Message-ID: <1309537527.2541.18.camel@Desktop666> (raw)
In-Reply-To: <BANLkTi=+jZCANpe8Bmh_7e6KNnQZjF35yA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2066 bytes --]
1) Native Long Polling Support
Not sure about this one, it would be useful, but preferably done once
Bitcoin is cleaned up anyway. A probable good way would be a central
notification interface which net, wallets, etc all connect to, including
things like a pool server. Thus I'm not sure about merging something
like this now.
2) A fix from Luke Dash Jr.
His branch is at
https://gitorious.org/~Luke-Jr/bitcoin/luke-jr-bitcoin/commits/getwork_dedupe and I would say it would be good to merge. gmaxwell indicated that hes been running this for a while and it is stable.
3) Hub Mode
Why? We dont have enough nodes listening to begin with, this generates a
ton of net usage on other listening nodes, which is not good. If you
open up your ports, you will get just as many, if not more connections
very easily.
4) RPC Turbocharge
Yep, this is something that is needed, there is also the other asio pull
request on github, not sure how/if these compare.
5) Resource Leak Fix
Looks good to me.
Matt
On Fri, 2011-07-01 at 18:03 +0200, Christian Decker wrote:
> Some appear to be beneficial to everybody.
> Multithreading the RPC will certainly speed up quite a few services
> and I see no downside in adding it. The same is true for Keep-Alive.
>
> I'm against including the long polling support because incredibly few
> people will benefit from it (pool providers) and yet it is included
> for everyone.
>
> The Hub mode is good, and I would go a step further and optimize the
> connection logic for all nodes by default.
>
> Just IMHO
>
> Regards,
> Chris
>
>
> On Fri, Jul 1, 2011 at 5:23 AM, Jeff Garzik <jgarzik@exmulti•com>
> wrote:
> This was posted to IRC:
> http://davids.webmaster.com/~davids/bitcoin-3diff.txt
>
> Includes several useful features that all the big pools have
> been
> screaming for... notably HTTP/1.1 keep-alive support.
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti•com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-07-01 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 3:23 Jeff Garzik
2011-07-01 16:03 ` Christian Decker
2011-07-01 16:23 ` Gregory Maxwell
2011-07-01 16:25 ` Matt Corallo [this message]
2011-07-01 18:59 ` Luke-Jr
2011-07-10 18:42 ` Luke-Jr
2011-07-10 19:12 ` Matt Corallo
2011-07-10 20:30 ` Luke-Jr
[not found] ` <1310335963.2230.29.camel@Desktop666>
[not found] ` <201107101846.09997.luke@dashjr.org>
2011-07-10 22:58 ` Matt Corallo
2011-08-04 20:29 ` Luke-Jr
2011-08-04 20:42 ` Luke-Jr
2011-08-04 23:43 ` Jeff Garzik
2011-08-05 3:01 ` Luke-Jr
2011-09-03 15:27 ` [Bitcoin-development] Last try: Fixes for 0.4 Luke-Jr
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=1309537527.2541.18.camel@Desktop666 \
--to=bitcoin-list@bluematt$(echo .)me \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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