I asked a BlazeDS engineer.  Below is the response:

Most of our messages have a ³small² format which is nothing but an
implementation of java.io.Externalizable.
Each of these message types has a baked-in class alias (registered with a
lookup table [aka class registry] on the server side) to facilitate
deserialization on the Java side. The class alias for CommandMessageExt is
DSC.
What this means is that if the deserialization code on the server
encounters a message with the alias DSC in it, it will attempt to
deserialize it as a CommandMessageExt.
 
As a reference, you will find other class aliases too: DSK, DSA etc.
spread across the BlazeDS and LCDS codebase.


-Alex

On 9/14/13 1:14 PM, "Philippe Bossu" <[email protected]> wrote:

>Hello,
>
>I am not sure if it's the right place to ask, if not sorry for noise.
>
>Anyway, is there somewhere a documentation about what DSC (
>http://grepcode.com/file/repo1.maven.org/maven2/com.adobe.blazeds/blazeds-
>core/3.2.0.3978/flex/messaging/messages/CommandMessageExt.java)
>messages are and their purpose and format ?
>Or does anybody on this list know already the answer ?
>
>Thanks for help.
>Regards

Reply via email to