Performing Inter Process Communication and AIDL

The canonical Android application comprises Activity and View objects on the front end and Intent and Service objects on the back end. As we discussed in chapter 3, activities are roughly comparable to UI screens, and views are UI components. When a user interacts with a screen, that screen usually represents a task, such as display a list of choices and allow selection, gather information through form input, or display graphics and data. Once each screen is finished with its individual job, it usually hands off to another component to perform the next task.

In Android terms, "hand off to another component" is done with an Intent. We introduced this concept and term in chapter 1, and we saw some limited amounts of Intent-related code in our examples in chapter 3. In this chapter we are going to expand on the details, including looking more closely at what exactly an Intent is and how it is resolved and matched with an IntentFilter. Along the way we will complete the RestaurantFinder application we started in chapter 3, finishing up

0 0

Post a comment