Next Gen Web Client Feedback

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?

Answer:
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?

Answer:

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?

Answer:

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.

Comments:

Post a Comment:
Comments are closed for this entry.
About

I'll be writing about topics that would interest users and developers of Sun Java Communication Suite.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today