In The Middle

Still More Web Middleware (Still Less HTTP)

While these solutions do something for offline enabling of static data (pages), they don't offer much help on more interactive Web systems, including relational database management systems (RDBMSes) or groupware system access. Forms, but not data, would be cached. Moreover, they are only beginning to be more than passive disks; only recently have prod ucts begun to make the cache have a mind of its own, for example, to download revised pages proactively during off hours. More active methodologies of pushing data out to disconnected sites or nodes are still on the drawing board.

Many Web-centric vendors finally are figuring out that they need help. The user-configurable screen saver PointCast, for example, has become a major contributor to corporate Internet link congestion and other related meltdowns. Every 15 minutes, a new weather map is downloaded to each subscribing client. PointCast has decided to work with Lotus to create a more intelligently distributed solution built on Notes, and Notes has the replication technology to handle the job.

When PointCast's next-generation solution is released, it will push the data once (and for all) inside the firewall, and desktop screen-saver clients will pull from that location. If PointCast enables IP multicasting next, it will be even further along. Moreover, this approach will give the corporation some way to control the settings for PointCast polling to make it more realistic than sadistic. The key is that Notes lets PointCast actively move the data locally. The model also gives PointCast a better way to sell to corporate users who now become a single aggregate customer, rather than a bunch of individual subscribers. I won't be surprised if ISPs don't get in on this soon. It's a nice way to differentiate yourself.

XcelleNet, the leader in disconnected client implementations, isn't standing still either. It is embarking on a new strategy for delivering applets and/or data primarily to offline users. With its next-generation subsystem controlling applet delivery and data replication, XcelleNet can maintain its edge in disconnected fat client enablement. The vendor's only competition today, really, is Notes. In fact, it would make sense for XcelleNet to work closely with desktop RDBMS vendors (specifically Sybase with its successful SQL Anywhere/Remote implementation) to tie in a better local database to comp ete with Notes. XcelleNet offers enhancements to Exchange and Notes interaction, not the least of which is controlling all remote-enabled applications with a single connection scheduler. A single call does it all.

As long as we continue to pay for connectivity by the minute (or packet), we'll need offline applications. Again, HTTP will lose out, since it doesn't solve the remote disconnected user need. If HTTP only exists to send static HTML pages to users and to be the menu system for downloading applets, then this functionality can be easily replaced by e-mail or other store and forward mechanisms for applications that can handle offline enablement.

That's not all applications, certainly. Many still need that online model for interactivity because it would be too hard to replicate their data. But, the model will work for many applications. The key is deciding what kind of application you've got.

Bruce Robertson is a program director with the META Group's Global Network-ing Strategies service. He can be reached at BruceR@metagroup.com.