polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Merlin <p...@nosphere.org>
Subject Re: ValueDeserialization help requested
Date Mon, 13 Jul 2015 10:01:05 GMT
Hey Niclas,

Yep, serialization is pretty straight forward.
Deserialization is a bit more convoluted.

That is to support streamed (de)serialization of large datasets like
giant Entities/Values or large collections of these.

Serialization is always streaming.
Deserialization is streaming by default (pull parsing) but may switch to
plain tree parsing when needed (eg. _type). This is what makes the
deserialization a bit complex.




Niclas Hedhman a écrit :
> Paul (I guess is the only one with much clue),
> Although I quite easily managed to add the feature of "object notation" (vs
> the key/value notation) to map serialization, the deserialization case is
> much harder to understand, and I am at loss where this decision and code
> really occurs.
> I have a hard time following the "flow", and wonder if the approach is
> actually optimal at all. Shouldn't the input be parsed, and then create the
> 4 functions to feed into ValueBuildFactory.newValueBuilderWithState(), or
> is that approach not possible due to some internal dependency?  Or was this
> concocted before the newValueBuilderWithState() existed?
> Any pointer/help is appreciated.
> Cheers

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message