node.js integration with chromium, next, what about mongo shell ?

[aureli...@gmail.com]

Hello,

If I correctly understand the wiki, node.js integrates with chromium, while preserving their two respective contexts and sharing the same execution engine: V8.

Now, according to the MongoDB site, "In 2.4 the default JavaScript engine in the mongo shell mongod is now V8."

So, theoretically, it would also be possible to integrate the mongo shell main loop into chromium and doing some context bridging between the processes, is that right?

[Roger]

<aureli...@gmail.com> writes:

> Hello,
>
> If I correctly understand the wiki, node.js integrates with chromium, while
> preserving their two respective contexts and sharing the same execution
> engine: V8.
>
> Now, according to the MongoDB site, "In 2.4 the default JavaScript engine

> in the mongo <http://docs.mongodb.org/manual/reference/mongo/#bin.mongo>shell
> mongod <http://docs.mongodb.org/manual/reference/mongod/#bin.mongod> is now

> V8."
>
> So, theoretically, it would also be possible to integrate the mongo shell
> main loop into chromium and doing some context bridging between the
> processes, is that right?

You're right. The other dependency is whether the event loop used there
is friendly to be embedded.

--
Roger

[aureli...@gmail.com]

This is quite interesting.

If someone could point out to me what really means "contexts" inside node-webkit, it could be helpful.

Sorry if I'm asking dumb questions, as I'm not a developer, just trying to understand the global architecture of the application.

So, does it mean that nodejs and webkit work in different threads, or that there are multiple instances of v8 into a same thread ?

Or, does it refer to concurrent javascript executions inside a single instance of v8 ?

Thanks for any hint onto this question.