summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRyan Dahl <ry@tinyclouds.org>2019-05-20 14:19:16 -0400
committerRyan Dahl <ry@tinyclouds.org>2019-05-20 15:22:08 -0400
commit9620b20edebdc40e97658caeef5de621881df1f5 (patch)
tree467b39a646328b2b412339838c5dced8ff568c4f
parent4a52fd7b61111c3c6f40453309e93d85d13b4547 (diff)
Adjust core/README.md text
-rw-r--r--core/README.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/core/README.md b/core/README.md
index 857bd672b..9345b6eff 100644
--- a/core/README.md
+++ b/core/README.md
@@ -4,9 +4,11 @@ This Rust crate contains the essential V8 bindings for Deno's command-line
interface (Deno CLI). The main abstraction here is the Isolate which provides a
way to execute JavaScript. The Isolate is modeled as a
`Future<Item=(), Error=JSError>` which completes once all of its ops have
-completed. The user must define what an Op is by implementing the `Dispatch`
-trait, and by doing so define any "built-in" functionality that would be
-provided by the VM. Ops are triggered by `Deno.core.dispatch()`.
+completed.
+
+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.rs](https://github.com/denoland/deno/blob/master/core/examples/http_bench.rs)