WebORB 3.0 - What's Next (Flex Messaging, RTMP for .NET)

We will be releasing WebORB 3.0 Professional Edition into production next week. We're adding a few more configuration panels to the console, so it will be even easier to make any configuration changes in the final release.

Around the same time we'll be releasing the first Beta of the long-awaited Enterprise Edition. In addition to all the features available in the Professional Edition, the product includes a powerful platform enabling a new generation of highly dynamic, real-time messaging products. Here's a little preview of the features to be available in Beta 1:

• Flex Messaging - backend support for MXML Consumer and Producer elements/APIs
• Integration with MSMQ. Flex Messaging destinations can be configured to integrate with MSMQ queues. Any message sent by a Flex Producer to a destination is put onto the corresponding MSMQ queue. Likewise Flex Consumers automatically receive any messages from the queue the subscribe to (through a destination)
• Messages can be sent not only by Flex clients, but native applications too. A windows application can put a message onto a queue, and WebORB will deliver it to all registered Flex consumers
• Remote SharedObject support. WebORB Enterprise provides a runtime environment for Remote SharedObjects. Flex and Flash applications can easily exchange information in real-time through dynamically constructed shared objects. In addition to client-side support, any server-side .NET class (or application) can register to receive/publish data from/to shared objects
• Video streaming - WebORB Enterprise provides a mechanism enabling audio and Flash video streaming. FLV files deployed with weborb can be easily streamed to any Flex/Flash client.
• Client-to-client streaming. A Flex/Flash client with a camera and/or microphone can easily publish a stream to the server so it can be rebroadcast to any other connected client. Alternatively, the stream can be recorded on the server for a later playback.
• Standalone and hosted execution modes. All the features listed above are available either by hosting the product in IIS or executing it as a independent standalone process. It is important to note that the standalone mode also support basic Remoting invocations over the RTMP channel, so an HTTP server is not required.
  

Stay tuned for more announcements.