By jhawk on Dec 21, 2007
Yahoo News: The 15 Biggest Tech Disappointments of 2007
#1 Windows Vista
#2 High-Def Format War
#5 Apple iPhone's Pricing Snafu
Some of the comments on my earlier post on "Start Thinking about Sun's New Web Communication Client!"
Q: Why does Sun still require mshttpd? Why do we need an additional layer?
The mshttpd server provides an established interface for our Web Mail Access Protocol (WMAP). The mshttpd process has been in place for nearly 8 years going back to Netscape Messaging Server 4.15sp7. We felt it eliminated a lot of risk by leveraging the existing HTTP services. This process is also required for legacy support of our Sun Java Systems Communication Express (UWC) client.
Q: Why does mshttpd only talk IMAP to a Sun Message Store? Will mshttpd support 3rd Party IMAP Servers in the future?
The mshttpd server uses a number of Sun's private extensions to IMAP. Namely.. Proxy Authentication. These extensions are not part of the open standards of IMAP. It is on the roadmap to support 3rd Party Servers in our new Web client.
Q: Why won't we support the Opera Browser?
The Opera Browser was considered. It is supported by the Ajax toolkit used in the Web Client, however we are narrowing our focus to ensure we have a solid release on more established browsers such as Microsoft Internet Explorer and Mozilla's Firefox.
As some of you have read on Jim Parkinson's Weblog.. As the Vice-President of Communications Software says.. we are definately going for a "Wow Factor." The exciting new AJAX-based client (code named Kendo) will be available in the first half of CY2008. While you are waiting for this product to arrive, we would like to outline some of the requirements that would be needed to allow you to deploy this new client.
The above image demonstrates the three components to the new Kendo client: the web browser, the web container, and the communications services.
The new web client utilizes Ajax to provide a "rich" user experience. The objective is to avoid potential complications brought in by plugins such as Flash. This means we are trying to focus on using the capabilities common within the most popular types of web browsers: Microsoft Internet Explorer, Mozilla FireFox, and Apple Safari.
The new client is built on some of the latest in Web 2.0 technologies. These technologies require a Web Container which has Glassfish and Grizzly capabilities. The supported web container for the Kendo client will be Sun Java System Application Server 9.1. The changes would remove the Sun Java Web Server as a supported Web container.
The Kendo client will require the mshttpd which is included in the Sun Java System Messaging Server 7.0. In most cases, the mshttpd will run on the same server as the Kendo Web Container. The mshttpd will evaluate WebMail requests against LDAP entries to proxy IMAP connections to the back-end Message Store servers.
The back-end Message Store servers will be required to be the equivalent to Messaging Server 6.3. Earlier 6.x versions must be at patch level 120228-25 or higher (see patch readme). Messaging Servers running on prior releases must upgrade to use the Kendo client.
Directory / Schema
Kendo will support Sun Java Systems Directory Server Enterprise Edition 6.x. The new Kendo client adds some additional attributes to the existing schema. Kendo will support both the old schema (schema 1) and the current schema (schema 2).
I'll be writing about topics that would interest users and developers of Sun Java Communication Suite.
No bookmarks in folder