Re: [Nbd] [RFC PATCH] doc: In STRUCTURED_REPLY, make error types easy to recognize
- To: Wouter Verhelst <w@...112...>
- Cc: "nbd-general@lists.sourceforge.net" <nbd-general@lists.sourceforge.net>
- Subject: Re: [Nbd] [RFC PATCH] doc: In STRUCTURED_REPLY, make error types easy to recognize
- From: Alex Bligh <alex@...872...>
- Date: Sat, 9 Apr 2016 12:22:09 +0100
- Message-id: <E1AE283B-D54E-4955-AD0E-F2A8AA546728@...872...>
- In-reply-to: <20160409104438.GP19023@...3...>
- References: <1460134137-3432-1-git-send-email-eblake@...696...> <B76616D0-B2F3-4313-9B94-B178C4A72828@...872...> <570815AA.6040201@...696...> <66657E74-4528-4558-81DA-299B2611110D@...872...> <20160409104438.GP19023@...3...>
On 9 Apr 2016, at 11:44, Wouter Verhelst <w@...112...> wrote:
> It's always easier to add new data at the end rather than in the middle.
> With the former, you can just use a struct to read data off the wire,
> and it won't change because someone changed the message. With the
> latter, that isn't the case.
+1, though ...
> (this is also pretty much how ASN.1 works, IIUC)
... IMHO ASN.1 is a design anti-pattern.
--
Alex Bligh
Reply to: