[Sugar-devel] Prototype python <-> js IPC

[Daniel Narvaez]

That option would also help a lot with memory too.

A MiniBrowser (C code only)
running manuq's clock takes ~10 mb per process. An activity (using
exec=sugar-html-activity) running the same takes > 30 mb.

I think that's not acceptable, we would have to go the
multiple-activities-per-process route which introduces interesting
problems. First of all with the current WebKit implementation the content
of multiple activities will be in the same process. Multiple content
processes are on the roadmap but there isn't even a bug for it yet, as far
as I can tell.


On 26 April 2013 15:12, Daniel Narvaez <dwnarvaez at gmail.com> wrote:

> So, lot of options here and not enough time to try all of them out.
> Though... I'm leaning towards having a websocket server in the sugar shell.
>
> Having system apis implemented in a separate process make sense from a
> security point of view. It also seems to be the same architecture as
> Firefox OS,
> https://wiki.mozilla.org/images/thumb/e/e2/B2G-processes.png/650px-B2G-processes.png
>
> I'm a bit worried about having to adapt the toolkit presence code to this
> model because it's fragile already but my gut feeling is that it's worth
> the pain.
>



-- 
Daniel Narvaez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20130426/42229b68/attachment.html>