The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted By |
Date submitted |
Date corrected |
| Printed |
Page 20
1st paragraph |
In the previous page (19), the author lists two purposes for specifying the process in which the component runs on:
"allow components that part of different apps but written by the same developer to run in the same process, or to let components that are part of the same app to run in different processes"
In page 20, the authors gives examples of these two purposes, but starts in reverse order. This was confusing.
"In the first case, you can let multiple components that normally run in one process instead[sic] run in multiple processes"
Note from the Author or Editor:
Two use cases are listed, but the introductory sentence contains the use cases in a different order than they are discussed, causing a bit of confusion. To resolve change pg 19 text from "allow components that part of different apps but written by the same developer to run in the same process, or to let components that are part of the same app to run in different processes" to "allow components that are part of the same app to run in different processes, or to let components that part of different apps but written by the same developer run in the same process" |
skim |
Jan 08, 2012 |
|
|
90
header |
It's embarrassing when you see wordos in the table of contents for a book.
In the section name "Input Validation: The Central Tenant of Application Security", the word "tenant" should be "tenet".
Note from the Author or Editor:
Mispelling. On p90, "tenant" should read "tenet". |
David M. Karr |
Dec 13, 2011 |
|
| PDF |
Page 6
United States |
In Chapter 1: Introduction page 6, where it says "A Short Bit on Device and User Account Security It is possible, and in some cases very desirable, for your application to learn about the security status of the device it is running on. Using the Device Management API, in-
troduced in Android 2.2, applications can determine password policies on devices, determine if device encryption capabilities are enabled, and other similar functions." the Author is referring to the Device Administration API. See http://developer.android.com/guide/topics/admin/device-admin.html for details.
Note from the Author or Editor:
The name was changed during/after writing. On p6, "Device Management API" should read "Device Administration API". |
Claudio J Lacayo |
Dec 07, 2011 |
|