Summary

This chapter has covered the higher-level communications APIs provided by Series 60. These allow developers to access sophisticated communications capabilities without needing to make direct use of relatively low-level technologies such as sockets and serial communications.

The HTTP section introduced the HTTP Client API added in Series 60 2.x. This can be used to create an HTTP session, make a simple request/response transaction, and receive notification of events occurring during the processing of that transaction.

The WAP section discussed the WAP protocol implementation, WAP stack architecture and connectionless versus connection-oriented sessions. The different APIs provided by Series 60 1.x and Series 60 2.x were also examined.

As shown in the Messaging section, Series 60 provides a number of APIs for creating and sending messages. The Client MTM API is the most powerful and fully featured but is also rather complex. For developers who just need to create simple messages and store them in the Drafts folder, the Send-As API was introduced. Finally, the CSendAppUi class was introduced as a convenient way to incorporate creation and sending functionality into an application's UI.

To complete the chapter, the Telephony section examined some common Telephony APIs: initiating calls, receiving incoming calls, and obtaining the phone's last calling number.