Re: Hierachy of autobean for state serialization

If I understand correctly, you want to persist/retrieve objects in the
client side. If there are not too many classes, you can define your
own format like
classId
versionId
binaryConvertedField1
binaryConvertedField2 ...

If your classes have collections or cross references or circular
references, the above approach woefully falls short.

With the classId, you can achieve polymorphism.
If the local storage does not permit binary data, you may have to
encode it as String.

J.Ganesan
www.DataStoreGwt.com

On Jun 2, 12:48 pm, Panam <pandem...@googlemail.com> wrote:
> Hm, I am just looking for a way to enocde and persist (webstore) state
> (some POJO properties) on the client.
> I have difficulties to see see how the RequestFactory will help me
> here as my intention is that it is for client server communication.
> However, it ought to be possible (at least, it has to do serialization
> to put the data on the wire).
> As I understand autobeans, they are that part of the bindery framework
> that is used for this purpose (amongst all by the request factory
> itself). That's why I am trying to use them here.
>
> Regards,
> panam

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.