Skip navigation
whather
Currently Being Moderated

Serialization Proxy

Oct 1, 2009 9:47 PM

I'm currently using BlazeDS for remote objects in my application and Red5 for RTMP streaming. The problem is, our Java objects need to be serializable between client-to-server for both Red5 and BlazeDS and Red5 uses the org.red5.io.amf3.IExternalizable interface and BlazeDS uses the java.io.Externalizable interface. I can't just implement the Externalizable interface because I don't want server-to-server serialization to use the custom serialization logic.

 

Is there a way to define custom serialization methods only for BlazeDS so I don't have to define the java.io.Externalizable interface? Or is there a serialization proxy I can use similar to the flex.messaging.io.PropertyProxyRegistry that let's me proxy the readExternal/writeExternal methods to custom ones? I see there is a flex.messaging.io.SerializationProxy (http://livedocs.adobe.com/blazeds/1/javadoc/) but I'm not sure how to use it.

 

Has anyone does this before? Thanks.

 

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points