Ah it's quite sad protostuff does not live up to the expectation :(
Compared to the google libs, streamlike is definitely a nice approach but I feel a bit sad to have to use marshallers and the read/write pattern. Having maintained compatibility of Java serializable object, such approach gives me the creep. How would your read code end up after a couple of evolutions, with ifs and other condition branches? There is no example in your tests that I could find.
Do you think either the protostuff approach or even protostuff itself is salvageable ? From a user point of view, I tend to like this approach more than the stream one. Especially since I don't have to do anything for the first schema version.
Emmanuel
ProtoStreams fits :)!
Many people seem to need such a library, that's why
protostuff
[1] project was created as an alternative, which sadly is quite
incomplete for our purposes (lacks support for schema evolution! -
unknown fields are just discarded) and does not seem to be
frequently maintained.
----------------
[1]
http://code.google.com/p/protostuff/
On 06/28/2013 09:39 PM, Manik Surtani wrote:
And
finally, if anyone could suggest a better name for the
stream-like package? I can't think of any other option
except streamlike :) (which might be
trade-marked) So any other options? If no options then we'll
just call it marshaling. I'll
move this to the ispn branch once I know the package name :)
Maybe it should be a separate project. I can imagine many
others finding such a library useful. ProtoStreams? :)
--
Manik Surtani
Platform Architect, JBoss Data Grid
_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev