Hello Fabrice

First, thank you very much for the explanation.

Now...

On 18/11/12 02:10, Fabrice Desre wrote:
Here's how the mozNotification API works : when you call
mozNotifications.createNotification(), an object is created in the
content process. This objects sends an IPC message to create a "dual"
object in the parent (chrome) process.
So what kind of IPC are you using? Binder?

And, another question, is the dual object a replication of the original
object or some kind of proxy object? Or maybe the object is put on
shared memory? I suppose it is some of the latter options because deeply
cloning the complete object would lead to a huge memory waste on the
parent process, more if the callback is a very nested closure with a lot
of references to other content process' objects.
Lastly, an IPC message is sent from the parent to
the matching child notification object to trigger the original JS callback.
It is great to see there is already a way to communicate data between
Gonk processes. I though this was technically impossible (for Gonk) at
present time.
Hope this helps,
A lot, ;)


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar 
nuestra política de envío y recepción de correo electrónico en el enlace 
situado más abajo.
This message is intended exclusively for its addressee. We only send and 
receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to