пт, 5 окт. 2018 г. в 21:43, Sage Weil <sage@xxxxxxxxxxxx>: > > On Fri, 5 Oct 2018, Vasiliy Tolstov wrote: > > пт, 5 окт. 2018 г. в 15:59, Paul Emmerich <paul.emmerich@xxxxxxxx>: > > > > > > I've also looked into handling the binary format two years ago; the > > > spec is the code and it's unfortunately not the best spec ;) > > > But the text version is really easy to handle, so we ended up using that. > > > > > > > Text version needs more space =). Also ceph uses binary format and if > > i want to write compatible software i need to handle binary form =( > > I think we're better of building the crush compile/decompile code in > library form to do the encoding/decoding for you. We periodically > change/extend the binary format and you're signing yourself up for future > compatibility problems. > > sage This is not problem because internal tests can easy detect this. (So simply i can create binary file from old text file with new ceph release and check parsing via test). -- Vasiliy Tolstov, e-mail: v.tolstov@xxxxxxxxx
