O'Reilly logo

SyncML®: Synchronizing and Managing Your Mobile Data by Phillipe Kahn, Peter Thompson, Apratim Purakayastha, Riku Mettälä, Uwe Hansmann

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Communication Toolkit API

The SyncML Reference Implementation comes with a communication API as a complementary component. It helps developers to access the underlying transports using a simple API. It currently supports HTTP [RFC2616] and OBEX [OBEX99]. Originally the support of WSP was also planned, but is not yet implemented. This is due to the fact that WSP would be only attractive to mobile phone platforms, as the supported client platforms can use HTTP instead. Also, the WAP APIs on each platform differ substantially. WSP [WSP01] clients connect to servers using a WAP Gateway, which transforms WSP into HTTP. Therefore servers do not need to contend with WSP, since they get the data via HTTP.

Figure 10-7 shows the architecture of the Communication ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required