Re: [android-developers] Re: ContentProvider storage/memory Q

2010-11-19 Thread Dianne Hackborn
This discussion probably belongs on android-platform; it is not really about the SDK. On Fri, Nov 19, 2010 at 9:11 AM, d1m_bu1b wrote: > Thanks for trying to address my question. > I have read all the references you suggested, that is how I have been > able to test its performance. > as I unders

[android-developers] Re: ContentProvider storage/memory Q

2010-11-19 Thread d1m_bu1b
Thanks for trying to address my question. I have read all the references you suggested, that is how I have been able to test its performance. as I understand it, the answer is: study all the Framwork code and figure it out yourself. more to consider: The Binder suggestion better illustrates my co

[android-developers] Re: ContentProvider storage/memory Q

2010-11-19 Thread d1m_bu1b
Thanks for trying to address my question. I have read all the references you suggested, that is how I have been able to test its performance. as I understand it, the answer is: study all the Framwork code and figure it out yourself. more to consider: The Binder suggestion better illustrates my co

Re: [android-developers] Re: ContentProvider storage/memory Q

2010-11-18 Thread Dianne Hackborn
On Thu, Nov 18, 2010 at 5:53 PM, d1m_bu1b 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

[android-developers] Re: ContentProvider storage/memory Q

2010-11-18 Thread d1m_bu1b
lets try again... 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. What cross partition IPC is recommended for "closer-to-real-time" latencies (~20ms)

Re: [android-developers] Re: ContentProvider storage/memory Q

2010-11-05 Thread Dianne Hackborn
ContentProvider doesn't define this (though the API is strongly designed around being backed by SQLite); it is up to the implementation of the content provider to decide how it will manage its storage. Look at the sample code for examples -- the NotePad sample is probably a good place to start. O

[android-developers] Re: ContentProvider storage/memory Q

2010-11-05 Thread d1m_bu1b
Any pointers? All I could find is a block diagram of SQL and a streamFile capability. There must be some documentation somewhere. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@google