[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - servlet transport implementation

[ataylor]

At the minute I'm still adding some jboss as 5 integration so i can run this, but in essence this is how i see it working.

On the client side we use the netty http transport to send messages to the servlet, there'll probably be changes needed around keep alive etc and I'll also use session id's in the Http requests.

On the server side we have 2 main components.

An HttpSessionListener which we use to maintain actual INVM connections. This means we can tidy up connections when sessions timeout. We can also control the timeout and have it configurable in the usual transport manner. Th einvm connection will be added to th eservlet context making it available in the servlet

The servlet itself. All this basically does is forward the content to th einvm connection and return any responses available.

Again, this will support true 1 - 1 request/response cardinality and I'll add support for both keep alive and separate requests.

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

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