Monday December 10, 2007 Start Thinking about Sun's New Web Communication Client!
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.
(click to enlarge image)
The above image demonstrates the three components to the new Kendo client: the web browser, the web container, and the communications services.
Web Browser
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.
Web Container
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.
Messaging Server
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).
Technorati Tags: ajax, dojo, glassfish, Grizzly, instant messaging server, messaging server, uwc
( Dec 10 2007, 01:32:41 PM PST ) Permalink
Comments [5]
Comments are closed for this entry.
test
Posted by s on December 10, 2007 at 05:47 PM PST #
"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."
Please, include Opera!
It is great opportunity to make a web client opera-users friendly!
I don't know why Sun ignores this great browser.
Peter
Posted by Piotr on December 11, 2007 at 03:58 AM PST #
Jonathan,
why not make new web client talk imap to the store or mmp? Just trying to understand reasoning behind introducing another protocol (WMAP) and keep using mshttp. It would make deployments so much easier if front end tier would only require apps servers and not apps + messaging (mshttp).
Posted by 75.86.168.68 on December 11, 2007 at 07:31 PM PST #
Just to clarify:
"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."
Will that mean that message stores will _have to_ be Sun IMAP-servers? We have just renewd our email infrastructure to a new version of an open source IMAP-server and would like to use calendar-features of the suite, but keep our current ldap ( with schema changes ) and imap-servers.
Sun's offering looks promising though and look forward hearing more!
Posted by Heimo Laukkanen on December 12, 2007 at 01:46 AM PST #
Please take a look at my responses in my latest post.
http://blogs.sun.com/jhawk/date/20071213
Posted by Jonathan Hawkins on December 13, 2007 at 06:05 PM PST #