On Wed, Aug 15, 2012 at 11:57 PM, avner <[email protected]> wrote: > Hi all, > > Very interesting. I think both node-webkit and app.js take excellent > approaches. My understanding is that node-webkit goes all the way in merging > node and webkit into one message loop and v8 thread, while app.js keeps node > and webkit (CEF) in separate threads and performs clever bridging of > contexts between the threads. It seems app.js is robust and clean, but > limited, whereas node-webkit aims to be a full blown application platform > but may suffer from more stability issues due to the full merger. > > Also, in app.js, I did not see any example of node being called out of the > web page - I'm not sure its possible. All the examples I saw are window > calls being made from the node side of the code. > > I'd be interested to know if these architectural differences seem right to > other people?
On node-webkit you are partly right, node-webkit is an appliaction platform while appjs is more a node module. But I don't think the way we merge node and webkit is unstable, we have a wiki page on our github describing it [1], it works out of box and there is no fancy magic in it. As for appjs, node.js and webkit are indeed running in two processes, bridge between them is done by IPC [2]. The way they did that is clever, but this kind of clever means dirty and slow and unstable, it may work sometimes and may fail in other times, while node-webkit just works. [1] https://github.com/rogerwang/node-webkit/wiki/How-node.js-is-integrated-with-chromium [2] https://github.com/appjs/appjs/blob/master/lib/bridge.js -- Cheng Intel Open Source Technology Center -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" 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/nodejs?hl=en?hl=en
