On 8 juil. 2013, at 21:06, Mircea Markus <mmarkus(a)redhat.com> wrote:
On 1 Jul 2013, at 09:29, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
> 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?
Compared with serializable objects, ProtoStream offers runtime validation based on the
proto file which should help maintenance.
> There is no example in your tests that I could find.
>
> Do you think either the protostuff approach or even protostuff itself is salvageable
?
There were prototypes written with conversion between domain objects and protoXyz
generated classes and the code quite ugly.
What is ProtoXyz? Anyways, I thought Protostuff was doing just that: runtime binding of a
domain model. You are saying that the generated code of ProtoStuff was crap?
> 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.
Cheers,
--
Mircea Markus
Infinispan lead (
www.infinispan.org)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev