public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Christian Decker <decker.christian@gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Useful bitcoin patches...
Date: Fri, 1 Jul 2011 18:03:52 +0200	[thread overview]
Message-ID: <BANLkTi=+jZCANpe8Bmh_7e6KNnQZjF35yA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinus7PWNLJi9rEvTtSB93hjLKhFpg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]

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
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

[-- Attachment #2: Type: text/html, Size: 2097 bytes --]

  reply	other threads:[~2011-07-01 16:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01  3:23 [Bitcoin-development] Useful bitcoin patches Jeff Garzik
2011-07-01 16:03 ` Christian Decker [this message]
2011-07-01 16:23   ` Gregory Maxwell
2011-07-01 16:25   ` Matt Corallo
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='BANLkTi=+jZCANpe8Bmh_7e6KNnQZjF35yA@mail.gmail.com' \
    --to=decker.christian@gmail.com \
    --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