I tested the MemoryFile between threads just to make sure I was doing it correctly. My hope is to send data between processes using shared memory. It seems to defeat the purpose of shared memory to NOT be able to map memory between two separate apps. That's why they call it shared. Is this going to be supported in the near future?
On Jun 23, 2:17 pm, Dianne Hackborn <[email protected]> wrote: > Also, fwiw, there is no reason to use a MemoryFile to share between two > threads -- you can just make any object and share it between them. > > On Tue, Jun 23, 2009 at 12:14 PM, Marco Nelissen <[email protected]>wrote: > > > > > On Mon, Jun 22, 2009 at 1:29 PM, Alec <[email protected]> wrote: > > >> Hi, > > >> I've been able to send data via shared memory between threads within a > >> process using MemoryFile. I then tried to send data between a service > >> and an activity in different processes, but the data did not get > >> passed. The name for each call the MemoryFile's constructor was the > >> same. Is it possible to share data between processes using a > >> MemoryFile? > > > Two MemoryFiles with the same name don't automatically map to the same > > area. > > Currently the only way to use a MemoryFile across processes is to use > > hidden APIs, which you shouldn't do. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
