Lingo is a new lightweight remoting / messaging library that smells a lot like Indigo in simple ways. The main difference is that the model isn’t baked in with WS-* XML blah.
It is cool that you have control over the messaging exchange patterns, and can do things like JMX over JMS very easily.
Lingo is a lightweight POJO based remoting and messaging library based on Spring’s Remoting which extends it to support JMS and support a wide range of message exchange patterns including both synchronous and asynchronous message exchange.
Current supported message exchange patterns include:
- synchronous request-response (like RMI)
- one way messaging (asynchronous invocation – like a JMS publish)
- asynchronous consumption (like a JMS subscribe)
- asynchronous request-reply (allowing the server side to asynchronously send one or more replies as the data becomes available).
You can think of Lingo as being conceptually similar to both Microsoft Indigo and JSR 181 in that it allows asynchrnous method execution, remoting and asynchronous messaging to be bound to existing POJOs (classes or interfaces) though it has no particular dependency on Web
Lingo supports pluggable messaging bindings; the first binding is an efficient JMS implementation. Over time we’ll be adding other bindings to web services frameworks and other transports.
Read more about the new: Lingo