From: Tamas Blummer <tamas@bitsofproof•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Missing fRelayTxes in version
Date: Thu, 20 Jun 2013 09:30:29 +0200 [thread overview]
Message-ID: <4DE0E45E-BB48-4DFF-9C86-ACBE312B3049@bitsofproof.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 388 bytes --]
Hi Mike,
The issue with the current parser is that those fields are conditionally optional on that there will be no subsequent fields added.
If there will be further fields they will become manadory.
Why not bump the version and parse the fields as mandatory from then on? This would be backward compatible and cleaner
going forward.
Tamas Blummer
http://bitsofproof.com
[-- Attachment #2: Type: text/html, Size: 5308 bytes --]
next reply other threads:[~2013-06-20 7:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 7:30 Tamas Blummer [this message]
2013-06-20 7:36 ` Mike Hearn
2013-06-20 8:17 ` Tamas Blummer
2013-06-20 8:31 ` Mike Hearn
2013-06-20 8:39 ` Tamas Blummer
2013-06-20 9:06 ` Pieter Wuille
2013-06-20 9:17 ` Mike Hearn
2013-06-20 10:37 ` Turkey Breast
2013-06-20 10:50 ` Mike Hearn
2013-06-20 10:52 ` Pieter Wuille
2013-06-20 10:58 ` Mike Hearn
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=4DE0E45E-BB48-4DFF-9C86-ACBE312B3049@bitsofproof.com \
--to=tamas@bitsofproof$(echo .)com \
--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