![]()
Web
Messaging
Web
content providers are enhancing their offerings by including
frequently updated data like stock quotes and sports scores.
Initially providers have used standard synchronous techniques
to pull data from Web servers. However, asynchronous (push)
messaging fits the task more naturally, providing more timely
data delivery with greater efficiency. Current products from
established message-oriented middleware providers, including
IBM, have been designed for server-based and desktop
applications, where manipulation of message information is
often more important than its presentation. Web Messaging
provides a declarative programming model suitable for the
presentation needs of Web application developers. It also
provides client and server runtime elements that have been
optimized for browser operating environments.
In Web Messaging, we enhance the integration of messaging
in Web applications in three ways. First, Web developers
exploit messaging declaratively, through markup and style
sheets, rather than through procedural programming. Second,
the additional client function required by Web Messaging is
carefully structured to minimize download time, to not
disrupt Web user experience. Third, asynchronous message
transport over the predominant Web protocols, HTTP and HTTPS,
is optimized, allowing a messaging server to support Web
clients more efficiently. The Web Messaging client is
constructed to support messaging into standard browsers
without specialized plug-ins or signed componentry (ActiveX
). We have also built a pure Javascript-based Web Messaging
client that can handle multiple platforms as well as
different browsers.
A Web Messaging based Java Server Faces Widget Library is
recently built to enable push-based real time data refresh on
portlets. This allows Web Authors to create dynamic content
by simply dragging a Web Messaging control to a Web page
using RAD 6.x (Rational Application Developer).
We have developed a demonstration of a financial
application that pushes real-time stock updates to both HTML
pages and portlets using WMQ Event Broker 2.1 or WBI Event
Broker 5.0.2.
Group Members
Gerry Buttner, Chitra Dorai, Jianren Li.
Alumni
Sameh Fakhouri, Kevan Miller.
|
