• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint

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 API. The Communication Manager layer shields the application developer from directly dealing with the different underlying layers. The application just needs to select the appropriate transport and to pass the settings for this transport to the Communication API. This generic approach enables an application to support the transports supported by this API, without writing much extra code for each transport.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint