In the following we examine the new Inter-Process Communication mechanisms available to applications and servers in Symbian OS. Understanding when and how these are required is essential in properly architecting components and making optimum use of the OS capabilities. Each of these mechanisms has its own strengths and limitations, so utilizing the right one will result in cleaner, more efficient programs that are easier to understand and maintain. Evolution of Symbian OS architecture Symbian OS so far has offered semaphores, shared memory, mutexes and client/server IPC mechanisms. Since the whole OS was architected from the ground up around event-driven user-initiated interactions, the communication mechanism of choice for most user-space components was client/server session-based IPC. The focus has always been on providing responsiveness to human users, while enabling many components and applications to share services and resources. These services and resources were always accessed through user-side servers that mediated access to them; hence the ubiquitous use of the client/server IPC
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.