In the example they expect you to implement IExternalizable. This is only needed if you want to preserve properties that do not have both a getter and a setter. In most cases a public var is enough, then you wont have to implement the IExternalizable.
"I wanted to know, can I then just send the AMF object to a server and store it as a binary in a mysql database? And also is this adviceable?" I have used this approach to store typed and complex data that is only used in Flash. I love it :) Greetz Erik On Thu, Aug 28, 2008 at 7:00 PM, Jiri Heitlager < [EMAIL PROTECTED]> wrote: > I came across a post on storing custom classes as an AMF object. It > explains how to do the following. > > "If you ever need to store the state of a custom object in a ByteArray or > SharedObject, or send a custom object through a LocalConnection, there are a > few simple steps you can take that will allow your object's state to be > serialised (converted to AMF) and preserved for future restoration. > " > src: http://www.si-robertson.com/go/serialise-custom-classes > > > I wanted to know, can I then just send the AMF object to a server and store > it as a binary in a mysql database? And also is this adviceable? > > Thank you, > > Jiri > > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
