Re: [Bitcoin-development] Adding request/reply id in messages

2012-04-12 Thread Wladimir
> > > I don't understand why you say my proposal would make the protocol more > stateful. I think it doesn't. > Each reply is only the result of the current request only, and there is > no new session information. > I also wondered this. My first thought was that it's basically the same as the PI

Re: [Bitcoin-development] Adding request/reply id in messages

2012-04-12 Thread Christian Bodt
On Thu, Apr 12, 2012 at 7:24 PM, Amir Taaki wrote: > Jeff elaborated the problems very well, but I just want to add this: > > Your change is essentially relying (trusting) the server to track a piece > of information (your state). No, it is more about distinguishing between replies (multiple as

Re: [Bitcoin-development] Adding request/reply id in messages

2012-04-12 Thread Peter Vessenes
to trigger the next round. It's > be better if there was no state whatsoever. > > > From: Jeff Garzik > To: sirk...@gmail.com > Cc: bitcoin-development@lists.sourceforge.net > Sent: Thursday, April 12, 2012 6:12 PM > Subject: Re: [Bitcoin

Re: [Bitcoin-development] Adding request/reply id in messages

2012-04-12 Thread Amir Taaki
tcoin-development] Adding request/reply id in messages On Wed, Apr 11, 2012 at 2:39 PM, Christian Bodt wrote: > Hi, > > I would like to discuss the following bitcoin protocol improvement proposal: > >          Adding request/reply id in all messages (in the message header, > based o

Re: [Bitcoin-development] Adding request/reply id in messages

2012-04-12 Thread Jeff Garzik
On Wed, Apr 11, 2012 at 2:39 PM, Christian Bodt wrote: > Hi, > > I would like to discuss the following bitcoin protocol improvement proposal: > >          Adding request/reply id in all messages (in the message header, > based on what was done for the "checksum" field) > > The original reason is t

Re: [Bitcoin-development] Adding request/reply id in messages

2012-04-12 Thread Christian Bodt
> For example, doing a second > identical "getblocks" request will not result in more "inv" replies, as > the client > prevents retransmits. Yes, the current prototype implementation modifies that. "getblocks" always results in one "inv" with [0-500] elements. It also removes the filtering on pre

Re: [Bitcoin-development] Adding request/reply id in messages

2012-04-12 Thread Amir Taaki
-development] Adding request/reply id in messages On Thu, Apr 12, 2012 at 11:41:05AM -0400, Gavin Andresen wrote: > On Wed, Apr 11, 2012 at 2:39 PM, Christian Bodt wrote: > > I would like to discuss the following bitcoin protocol improvement proposal: > > > >          Adding re

Re: [Bitcoin-development] Adding request/reply id in messages

2012-04-12 Thread Pieter Wuille
On Thu, Apr 12, 2012 at 11:41:05AM -0400, Gavin Andresen wrote: > On Wed, Apr 11, 2012 at 2:39 PM, Christian Bodt wrote: > > I would like to discuss the following bitcoin protocol improvement proposal: > > > >          Adding request/reply id in all messages (in the message header, > > based on wh

Re: [Bitcoin-development] Adding request/reply id in messages

2012-04-12 Thread Gavin Andresen
On Wed, Apr 11, 2012 at 2:39 PM, Christian Bodt wrote: > I would like to discuss the following bitcoin protocol improvement proposal: > >          Adding request/reply id in all messages (in the message header, > based on what was done for the "checksum" field) That seems like a perfectly reasona