[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

[timfox]

The code in TRUNK doesn't use remoting serialization managers at all any more.

I was fed up with the fact that remoting always passed in an ObjectOutput/Input Stream, so I have created new subclasses of ObjectOutput/InputStream called MessagingObjectOutput/InputStream which basically are just a thin wrapper over a straightforward DataOutput/InputStream.

This means we can have full control over the bytes we write to the stream without having to worry about all the other serialization header rubbish being written that we don't need.

The only times we need to serialize stuff is for non performance critical invocations and for object messages containing a user provided object that we don't know until runtime.

In these cases i just create an object output/input stream on the fly and serialize to the dataoutputstream.

So the value of serializationType in the uri is completely ignored.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973381#3973381

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973381