View post: Shiny new remoting layer for JBM
Navigation
Recent posts from all feeds
- hSenid - officially certified JBCP partner
- jBPM 3 seam/jsf/richfaces based console
- Help push the open sourcing of a jBPM Migration Tool
- JBUG Munich meets Pete Muir with JSR-299 - Contexts and Dependency Injection for Java EE (06.07.09 at 19:00 PM)
- Javarsovia, static analysis and annotations
- Drools Job requested - Buenos Aires Argentina
- Seam and Web Beans downloads temporarily relocated
- Introducing a new smart forms tool: Drools Advisor
- JBoss Cloud introduction video
- Using rich:colorPicker in RichFaces
- « Back to feed: Tim Fox's messaging blog.
Shiny new remoting layer for JBM
I've just completed a refactoring of our JBoss Messaging remoting layer.This is a thin layer that sits between the majority of the JBM core code and the actual transport provider (E.g. Apache MINA).
Most of the leg-work is done in our remoting layer - ordering of sessions, pinging (heartbeats) etc.
The core remoting code now has zero dependencies on any particular transport provider. This means we can easily plug-in different providers with the minimum of pain - e.g. Apache MINA, Trustin Lee's Netty 3, and David Lloyd's XNIO.
Integrating a new transport provider is simple. JBM provides a spi (service provider interface) set of interfaces that need to implemented for each transport provider. Once that is done, you just add the ConnectorFactory and AcceptorFactory class names to the config file and you're done.
The implementations of the spi interfaces are typically very simple, since all the generic code is in our remoting layer and doesn't change.
