December 2008
Intermediate to advanced
443 pages
10h 24m
English
book
Common Design Patterns for Symbian OS: The Foundations of Smartphone Software
by Adrian A. I. Issott
Content preview from Common Design Patterns for Symbian OS: The Foundations of Smartphone Software
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
6.1. Client-Thread Service
Intent
Enable the re-use of code by rapidly developing a service that executes independently within the thread of each client.
AKA
Shared Library[]
6.1.1. Problem
6.1.1.1. Context
You wish to develop a service that can be re-used by a number of components, with clients of the service able to operate independently of each other.
6.1.1.2. Summary
It is expensive to create stand-alone code for each application that needs it.
Maintenance of multiple copies of such code usually doesn't scale well and is defect-prone.
Duplication of common code is memory inefficient in terms of both code size and RAM usage.
6.1.1.3. Description
Novice software developers often re-write similar code for each application – code that essentially performs the same actions and which may even be copied and pasted between projects.
This is a problem, and not just because re-writing code is expensive (and boring). Simplistic solutions such as copying and pasting do not scale well, because each new copy increases the cost of maintenance. In addition, the resources consumed across the system due to the additional code size, resulting from all the duplicated code, is unacceptable on constrained Symbian OS devices.
This problem occurs in all software problem domains, ranging from device creation to third-party application development.
6.1.1.4. Example
Calendar and contacts databases, and indeed any database, usually store their data using the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.