Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QcgXJ-0000yb-Oo for bitcoin-development@lists.sourceforge.net; Fri, 01 Jul 2011 16:25:45 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bluematt.me designates 208.79.240.5 as permitted sender) client-ip=208.79.240.5; envelope-from=bitcoin-list@bluematt.me; helo=smtpauth.rollernet.us; Received: from smtpauth.rollernet.us ([208.79.240.5]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1QcgXG-0007SP-KB for bitcoin-development@lists.sourceforge.net; Fri, 01 Jul 2011 16:25:45 +0000 Received: from smtpauth.rollernet.us (localhost [127.0.0.1]) by smtpauth.rollernet.us (Postfix) with ESMTP id 8C70D594012 for ; Fri, 1 Jul 2011 09:25:21 -0700 (PDT) Received: from mail.bluematt.me (unknown [IPv6:2001:470:9ff2:2:20c:29ff:fe16:f239]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: @bluematt.me) by smtpauth.rollernet.us (Postfix) with ESMTPSA for ; Fri, 1 Jul 2011 09:25:21 -0700 (PDT) Received: from [IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b] (unknown [IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b]) by mail.bluematt.me (Postfix) with ESMTPSA id 689673F4 for ; Fri, 1 Jul 2011 18:25:27 +0200 (CEST) From: Matt Corallo To: bitcoin-development@lists.sourceforge.net In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-2iMdOHlZkcehqWltNE1R" Date: Fri, 01 Jul 2011 18:25:27 +0200 Message-ID: <1309537527.2541.18.camel@Desktop666> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Rollernet-Abuse: Processed by Roller Network Mail Services. Contact abuse@rollernet.us to report violations. Abuse policy: http://rollernet.us/abuse.php X-Rollernet-Submit: Submit ID 6fbf.4e0df4f1.8552.0 X-Spam-Score: -1.5 (-) 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 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1QcgXG-0007SP-KB Subject: Re: [Bitcoin-development] Useful bitcoin patches... X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2011 16:25:45 -0000 --=-2iMdOHlZkcehqWltNE1R Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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_dedu= pe and I would say it would be good to merge. gmaxwell indicated that hes b= een 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. >=20 > 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. >=20 > The Hub mode is good, and I would go a step further and optimize the > connection logic for all nodes by default.=20 >=20 > Just IMHO >=20 > Regards, > Chris >=20 >=20 > On Fri, Jul 1, 2011 at 5:23 AM, Jeff Garzik > wrote: > This was posted to IRC: > http://davids.webmaster.com/~davids/bitcoin-3diff.txt > =20 > Includes several useful features that all the big pools have > been > screaming for... notably HTTP/1.1 keep-alive support. > =20 > -- > Jeff Garzik > exMULTI, Inc. > jgarzik@exmulti.com --=-2iMdOHlZkcehqWltNE1R Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAABAgAGBQJODfTwAAoJEBrh01BD4I5UDEsQALgl7uA3RJXpWRGR+r5Se/R2 c3cdxKd0+HiLNG/ycUQlDSFJg3Sl/QP4YFoZ9Is+m4YltyZfO/VYsFS3guXiZ3fC luLJUoJZGCjomrYNbbg6mYhUu+HSUt+iX9uUvSCtO83FdhXOeKBp9m/6FXIFQXHO 8ihXJ/OqylyouvUVVEfdDdIcto07QbJEuHAIzwD9wUfOMI4EgBb5fCDrYW9kNboz QKDlXaifLjxEnp2wSgW0FR+lOdawDqmjovq8HlfB3K6WGn/pP5rsjxizDHR1/dpm j01V5FlkrS9aJz9lzWlkbZ+NJd36DJTTJY1FQSubn0S7gD2T7TofaPboiJScYg96 RiY+ZnD+6UQxbn3BPNLAHP1YDeZ59nxWyQ1gMYXfMniQwusxsau5raL0ltWQ1hWc 9z0MxG1oLHTiqm2LG6h9BEJ/GaPGFEL3KAnUWF+NFtBJ+vBEQNksZeYMfnEy32T4 6xRVzU60N3TfMp6FL66ZaYvINbZTz/11IN9KSJKgn5eOK5IUWoCSfAADPJHEfGmy zZEIV/86jZ6+rlTpJSBQC/4XUgnQHnDAnkj19Igjaak4Hy7Ti777+/cMwQe6J1hH CYu8mh6P1/f5JoParMuFk7NCF6XJlQpxFTLW/ma7zrB/vPnIAutAeOUmtLyFfGY8 Y0QDV/ZFWptUwUKXWbB9 =sOps -----END PGP SIGNATURE----- --=-2iMdOHlZkcehqWltNE1R--