summaryrefslogtreecommitdiff
path: root/f8/7a9c9a11e1137085c57d674e19b4b5a9621268
blob: dfa7a678118d64db462d1ce76d776bccb3878e25 (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
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <decker.christian@gmail.com>) id 1QcgCt-0007zu-AN
	for bitcoin-development@lists.sourceforge.net;
	Fri, 01 Jul 2011 16:04:39 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.210.47 as permitted sender)
	client-ip=209.85.210.47;
	envelope-from=decker.christian@gmail.com;
	helo=mail-pz0-f47.google.com; 
Received: from mail-pz0-f47.google.com ([209.85.210.47])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1QcgCs-0006j9-5N
	for bitcoin-development@lists.sourceforge.net;
	Fri, 01 Jul 2011 16:04:39 +0000
Received: by pzk36 with SMTP id 36so1077637pzk.34
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 01 Jul 2011 09:04:32 -0700 (PDT)
Received: by 10.68.30.68 with SMTP id q4mr4034395pbh.435.1309536272044; Fri,
	01 Jul 2011 09:04:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.64.36 with HTTP; Fri, 1 Jul 2011 09:03:52 -0700 (PDT)
In-Reply-To: <BANLkTinus7PWNLJi9rEvTtSB93hjLKhFpg@mail.gmail.com>
References: <BANLkTinus7PWNLJi9rEvTtSB93hjLKhFpg@mail.gmail.com>
From: Christian Decker <decker.christian@gmail.com>
Date: Fri, 1 Jul 2011 18:03:52 +0200
Message-ID: <BANLkTi=+jZCANpe8Bmh_7e6KNnQZjF35yA@mail.gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=bcaec520ebb950d36b04a7042c61
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(decker.christian[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QcgCs-0006j9-5N
Subject: Re: [Bitcoin-development] Useful bitcoin patches...
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: Fri, 01 Jul 2011 16:04:39 -0000

--bcaec520ebb950d36b04a7042c61
Content-Type: text/plain; charset=ISO-8859-1

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
>

--bcaec520ebb950d36b04a7042c61
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Some appear to be beneficial to everybody.<br>Multithreading the RPC will c=
ertainly speed up quite a few services and I see no downside in adding it. =
The same is true for Keep-Alive.<br><br>I&#39;m against including the long =
polling support because incredibly few people will benefit from it (pool pr=
oviders) and yet it is included for everyone.<br>

<br>The Hub mode is good, and I would go a step further and optimize the co=
nnection logic for all nodes by default. <br><br>Just IMHO<br><br>Regards,<=
br>Chris<br>
<br><br><div class=3D"gmail_quote">On Fri, Jul 1, 2011 at 5:23 AM, Jeff Gar=
zik <span dir=3D"ltr">&lt;<a href=3D"mailto:jgarzik@exmulti.com">jgarzik@ex=
multi.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

This was posted to IRC:<br>
<a href=3D"http://davids.webmaster.com/%7Edavids/bitcoin-3diff.txt" target=
=3D"_blank">http://davids.webmaster.com/~davids/bitcoin-3diff.txt</a><br>
<br>
Includes several useful features that all the big pools have been<br>
screaming for... =A0notably HTTP/1.1 keep-alive support.<br>
<br>
--<br>
Jeff Garzik<br>
exMULTI, Inc.<br>
<a href=3D"mailto:jgarzik@exmulti.com">jgarzik@exmulti.com</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
All of the data generated in your IT infrastructure is seriously valuable.<=
br>
Why? It contains a definitive record of application performance, security<b=
r>
threats, fraudulent activity, and more. Splunk takes this data and makes<br=
>
sense of it. IT sense. And common sense.<br>
<a href=3D"http://p.sf.net/sfu/splunk-d2d-c2" target=3D"_blank">http://p.sf=
.net/sfu/splunk-d2d-c2</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br>

--bcaec520ebb950d36b04a7042c61--