Moreover, the encoding will never change in a backwards-incompatible way. If for some reason I invented a new incompatible encoding I'd give it a new name entirely.
(However, we may occasionally add new features which aren't understood by old versions, but such features would be opt-in.) -Kenton On Wed, Jun 7, 2017 at 9:20 AM, Ian Denhardt <[email protected]> wrote: > Yes. The encoding hasn't changed at all. > > Quoting Vitaliy Bondarchuk (2017-06-07 07:39:46) > > Hi > > I use cap'n'proto messages as storage format in NoSQL database. Can I > > continue use data with 0.6 prepared with older version? > > Thanks > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Cap'n Proto" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to [1][email protected]. > > Visit this group at [2]https://groups.google.com/group/capnproto. > > > > Verweise > > > > 1. mailto:[email protected] > > 2. https://groups.google.com/group/capnproto > > -- > You received this message because you are subscribed to the Google Groups > "Cap'n Proto" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > Visit this group at https://groups.google.com/group/capnproto. > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto.
