Comms Software Summit: Day 2 Recap

Day 2 of the Comms Summit was jokingly summed up by one of our more colorful attendees as "Death by slidedeck." Okay, there were a lot of presos to get through but the information was very valuable indeed.

For example, our Partner Enablement program conducts or is involved with various events, including security presos, a JavaCAPs summit, Immersion Week, CEC, Directory Masters Event, and so on. (NDA required.) There's a sharespace site as well that partners can get to where lots of information (including Comms info) is stored. The FAMtalk site was mentioned as well as a place to get podcasts. If you're a partner, there is lots out there, and while news to me, probably not to partners themselves.

Next, we heard from the president of Notify, which provides mobility solutions for Comms. The takeaways here for me were:

  • Notify supports lots of devices.
  • Notify started supported Comms as of the Java ES 3 release.
  • Notify supports lots of devices. (Yes, already said that. This is a big deal.)
  • Notify looks like a better fit for enterprises than ISPs (the solution is more oriented toward business than consumer).
  • Looks like we could do a better job from a doc perspective to help w/ the Comms/Notify intergration/deployment information. Something to look into, for sure.

One of the more interesting presos today was on Lemonade support in Messaging Server 7.0. For those not willing to read the actual RFCs, perhaps I can sum up what this gives you:

  • The standard is really intended for mobile clients. It reduces network traffic (volume and interactions), and moves the CPU load from client to server.
  • Main features:
    • Forward w/o download (see CATENATE, URLAUTH, and BURL)
    • Quick resync (see CONDSTORE AND QRESYNC)
    • Maintain a sorted view (see CONTEXT)
    • Converting (similar to FETCH); the only conversion in Messaging 7.0 will is a char set conversion (and not on headers yet)
    • Automatic push to clients (see NOTIFY).
For more information on Lemonade in Messaging Server 7.0, see Messaging Server Lemonade Profile 1 Support.

The other takeaway from this session for me was that, guess what, we're ahead of the game on getting in Lemonade support to our server. Now we need clients to take advantage of this code.

Comments:

We have been piloting Notify with our JES system and its great. It supports BlackBerry, Windows Mobile and Palm clients.

There does need to be more documents of how to setup Notify/JES together. We had to piece them together and I wouldn't say our setup is optimal. We use standard IMAP to grab our mail instead of setting the server to SUN. We are probably missing some nice features doing that.

The calendar/contacts/tasks works great but figuring out that some things point at the calendar store and some at UWC is a bit confusing. I think a little doc work could really help here.

just my .02

Posted by Ray on April 09, 2008 at 11:34 PM MDT #

Thanks for the feedback. Would like to help. I think there's room for Sun and Notify to both collab on some of this and produce some useful docs.

Posted by Joe Sciallo on April 10, 2008 at 03:02 AM MDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Reporting about Unified Communications Suite Documentation, including news, Comms 101, documentation updates, and tips and tricks.

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