Welcome to OpenDEN
Custom Search
Messaging Middleware
Messaging Middleware:
A messaging server is a middleware program that handles messages that are sent for use by other programs using a messaging application program interface (API). A messaging server can usually queue and prioritize messages as needed and saves each of the client programs from having to perform these services. Messaging and messaging servers usually are organized in one or both of two models: point-to-point messaging and subscribe/publish messaging.
From: http://searchwinit.techtarget.com/gDefinition/0,294236,sid1_gci214556,00.html
Lingo
Lingo is a lightweight POJO based remoting and messaging library based on Spring's Remoting which extends it to support JMS. Lingo can support a wide range of message exchange patterns including both synchronous and asynchronous message exchange.
Lingo is an ideal technology to cluster your POJO services to achieve load balancing across many servers and automatic failover. Lingo is high performance and works great in server centric environments as it can work with JCA to cleanly integrate with thread, connection and session pooling as well as handing of transactions, retry and exception handling.
Lingo now has SCA Support for working with the SCA annotations.
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 Services infrastructure.
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.
Lingo is an ideal technology to cluster your POJO services to achieve load balancing across many servers and automatic failover. Lingo is high performance and works great in server centric environments as it can work with JCA to cleanly integrate with thread, connection and session pooling as well as handing of transactions, retry and exception handling.
Lingo now has SCA Support for working with the SCA annotations.
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 Services infrastructure.
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.
Loading .....
Recently Viewed Categories
News Aggregation, RSS (.NET, Windows)
Internet TV, Video
Desk Top Publishing (DTP)
Network selector
Design (Systems)
Recently Viewed Products
