dd156e886b
I think it's a better fit since recv() was killed and opcall <> syscall (send/recv was too reminiscent of request/response and custom payloads) |
||
|---|---|---|
| .. | ||
| benches | ||
| examples | ||
| async_cancel.rs | ||
| async_cell.rs | ||
| bindings.rs | ||
| Cargo.toml | ||
| core.js | ||
| encode_decode_test.js | ||
| error.js | ||
| error.rs | ||
| flags.rs | ||
| gotham_state.rs | ||
| icudtl.dat | ||
| lib.deno_core.d.ts | ||
| lib.rs | ||
| module_specifier.rs | ||
| modules.rs | ||
| normalize_path.rs | ||
| ops.rs | ||
| ops_json.rs | ||
| plugin_api.rs | ||
| README.md | ||
| resources.rs | ||
| runtime.rs | ||
| serialize_deserialize_test.js | ||
| zero_copy_buf.rs | ||
Deno Core Crate
The main dependency of this crate is rusty_v8, which provides the V8-Rust bindings.
This Rust crate contains the essential V8 bindings for Deno's command-line interface (Deno CLI). The main abstraction here is the JsRuntime which provides a way to execute JavaScript.
The JsRuntime implements an event loop abstraction for the executed code that
keeps track of all pending tasks (async ops, dynamic module loads). It is user's
responsibility to drive that loop by using JsRuntime::run_event_loop method -
it must be executed in the context of Rust's future executor (eg. tokio, smol).
In order to bind Rust functions into JavaScript, use the Deno.core.dispatch()
function to trigger the "dispatch" callback in Rust. The user is responsible for
encoding both the request and response into a Uint8Array.
Documentation for this crate is thin at the moment. Please see http_bench_ops.rs as a simple example of usage.
TypeScript support and a lot of other functionality is not available at this layer. See the CLI for that.