Developer Resources:

Customer Quotes:

Real-Time Messaging

WebORB enables real-time messaging via its Publish-Subscribe exchange mechanism. Various enterprise software packages provide implementations of the publish-subscribe mechanism, namely Microsoft MessageQueue (MSMQ) or IBM's WebSphere MQ. WebORB includes its own implementation of message routing in addition to other publish-subscribe implementations (i.e. MSMQ, Windows Azure Queue and ApacheNMS). WebORB serves as an adapter between the supported clients and the actual message distributor.  Click on the following to learn more:

Rich Text Chat

Rich text chat is an interactive real-time conversation via text over mobile and non-mobile computing devices.  WebORB makes it easy to implement rich text chat in your web application through multiple mechanisms, such as through Remote Shared Objects and Publish-Subscribe.

Text Chat Using Remote Shared Objects Example>
Text Chat Using Publish Subscribe Example>

Data Push

Data push is the process of pushing data from a server over RTMP to all subscribed clients.  This messaging paradigm is often preferred as it alleviates a lot of network traffic and bandwidth consumption that comes with frequent client-side polling of server-side resources.  The data push model notifies the client whenever new data is ready for consumption.

While WebORB message routing does provide data push for both in-process and out-of-process data without any dependency on third party message queuing systems, it also supports data push via MSMQ and Apache NMS.

View Data Push from MSMQ to Flex>
View RTMP Data Push from .NET to Flex>
View Messaging Documentation>
View Data Push Sample Application>

Publish-Subscribe

Publish-Subscribe is a message exchange paradigm where one computer program (or just an object on a smaller scale) can subscribe to receive messages and another program (or an object) can publish messages. This functionality is ideally suited for subscription services or any use case that requires the delivery of time-sensitive data.

The publishing entity is called Producer, and the entity receiving messages is a Consumer. Various enterprise software packages provide implementations of the publish-subscribe mechanism, namely Microsoft MessageQueue (MSMQ) or IBM's WebSphere MQ. WebORB includes an implementation of the message routing mechanism with support for remotely located producers and consumers. Additionally, WebORB integrates with other publish-subscribe implementations (i.e. MSMQ, Windows Azure Queue) and can act as an adapter between the supported clients and the actual message distributor.

View Publish-Subscribe Documentation>
View Sample Text Chat Publish-Subscribe Application>

MSMQ Integration

WebORB's Publish-Subscribe Messaging integrates with MSMQ by connecting messaging destinations with MSMQ queues. WebORB automatically routes messages published to destinations to the corresponding queues. For the subscribers it acts as a proxy between a queue and the subscribed clients.

View MSMQ Message Routing Documentation>
View Data Push from MSMQ to Flex Article>

Apache NMS Integration

WebORB Publish-Subscribe Messaging integrates with Apache NMS by connecting messaging destinations with NMS destinations. WebORB automatically routes messages published to WebORB messaging destinations to the corresponding NMS destinations. For the subscribers it acts as a proxy between an NMS destination and the subscribed WebORB clients.

View Apache NMS Message Routing Documentation>

Remote Shared Objects

WebORB supports the Remote Shared Objects (RSO) API enabling clients to exchange data with each other or with the server.  RSOs are created and managed within the application scope.

View WebORB RSO Technical Article >
View Sample Text Chat Using Remote Shared Objects Application>
View WebORB 101 Remote Shared Objects Video>