Deno: some question about deno2

Created on 1 Jul 2018  路  1Comment  路  Source: denoland/deno

I have read roadmap.md, v8worker2 and jsconf.pdf to understand deno's architecture.
after read, I have some questions and want to check my understanding.

Questions.

  1. libdeno is similar concept with some c++ files in v8worker2 (like binding.cpp, binding.h)? and Just rewrite for rust code?
  2. Unprivileged part is composed like this ? [some rust code [libdeno [v8 engine, typscript compilrer] ] ] ( [] means wrapping ) and Where can I read deno2 readme.md?
  3. Is it still same architecture as follows image? If still same, what's mean exactly dispatcher? Dispatcher is written by only rust code? or rust code + libdeno?
    2018-07-01 7 16 01

thanks to read foolish questions.

Most helpful comment

1) Yes 2) Yes 3) Yes. Dispatcher was set of routines in the prototype implementation which doesn't exist yet in the rewrite.

There are other details that we haven't worked out yet that aren't described in the above figure. Example: whether to dedicate a thread for V8 or use a single threaded Node-like design (you can see some discussion of this in #301).

>All comments

1) Yes 2) Yes 3) Yes. Dispatcher was set of routines in the prototype implementation which doesn't exist yet in the rewrite.

There are other details that we haven't worked out yet that aren't described in the above figure. Example: whether to dedicate a thread for V8 or use a single threaded Node-like design (you can see some discussion of this in #301).

Was this page helpful?
0 / 5 - 0 ratings

Related issues

kitsonk picture kitsonk  路  3Comments

motss picture motss  路  3Comments

justjavac picture justjavac  路  3Comments

watilde picture watilde  路  3Comments

zugende picture zugende  路  3Comments