[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: New wireformat and client side remoting

[timfox]

"jmesnil" wrote : I've started to document the new Remote API on the wiki:  http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingNewRemoteAPI

This looks good :)

Some comments:

Can targetID and callback id be longs (or ints?) too?

I'm thinking that Java guids are pretty long, and we want to keep the packets as small as possible - maybe I'm being over conservative though...

Do connect and disconnect really belong on the RemotDispatcher?

Three different ways to exchange packets - the second way (e.g. send non persistent message) - in fact, non persistent messages can be fire and forget - non blocking request / response is not supported using the JMS API but is very useful for doing stuff over and above JMS which we can expose through the generic interface.

responses via HTTP - is this done by keeping the http connection open and sending responses that way? I can't see it work otherwise without polling.

http post: i can see that encoding requests as http params is not always going to work - especially if we have to tunnel through another web server who will limit http params to a max length - can we extend the http codec to do this differently?

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

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