On Thu, Nov 18, 2010 at 5:53 PM, d1m_bu1b <[email protected]> wrote:
> Insight into the underlying mechanisms and protocols can help > developer design the best IPC for their purposes. > Guessing at implementations and testing the performance is way too > time consuming. > You don't need to guess at implementations; all of the code you are curious about is open source for you to peruse. > What cross partition IPC is recommended for "closer-to-real-time" > latencies (~20ms) for transferring data from application to multiple > other applications running in the own Dalvik instances? > Pretty much any IPC mechanism you pick is going to be well below 20ms for the raw communication. We tend to prefer using Binder for higher-level parts of Android, as you can see with all of the SDK documentation on using this in apps. Does documentation describing best practices for using > ContentProviders exist? > The notepad example barely illustrates the outer layer of the onion as > does the ContentProvider.html page > The note pad example illustrates a best practice. I don't really understand what you seem to be implying about it not being a best practice in only illustrating "the outer layer of the onion" when it is in fact a complete working implementation of a content provider. > "though the API is strongly designed around being backed by SQLite" > Does this design exist in any documentation? > Um, all you need to do is look at the API. For example: http://developer.android.com/reference/android/content/ContentProvider.html#query(android.net.Uri, java.lang.String[], java.lang.String, java.lang.String[], java.lang.String) Pretty strongly (one might say even painfully) oriented around SQLite. > Where is the SW design for the ContentProvider? > There is quite a bit of documentation on it in the SDK, including the overall model for the APIs. If you are wondering about the implementation, have a look at the source code. > Does any documentation exist for the android Framework hierarchy in > the repo? > I guess I'll just search and look at the code. > The code is the authority. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
