溫馨提示×

溫馨提示×

您好,登錄后才能下訂單哦!

密碼登錄×
登錄注冊×
其他方式登錄
點(diǎn)擊 登錄注冊 即表示同意《億速云用戶服務(wù)條款》

實(shí)現(xiàn)deno通信的方法

發(fā)布時間:2020-07-08 14:21:11 來源:億速云 閱讀:238 作者:Leah 欄目:web開發(fā)

這篇文章將為大家詳細(xì)講解有關(guān)實(shí)現(xiàn)deno通信的方法,文章內(nèi)容質(zhì)量較高,因此小編分享給大家做個參考,希望大家閱讀完這篇文章后對相關(guān)知識有一定的了解。

通信方式

deno執(zhí)行代碼和node相似,包含同步和異步的方式, 異步方式通過Promise.then實(shí)現(xiàn)。

Typescript/Javascript調(diào)用rust

在上一節(jié)中講到deno的啟動時會初始化v8 isolate實(shí)例,在初始化的過程中,會將c++的函數(shù)綁定到v8 isolate的實(shí)例上,在v8執(zhí)行Javascript代碼時,可以像調(diào)用Javascript函數(shù)一樣調(diào)用這些綁定的函數(shù)。具體的綁定實(shí)現(xiàn)如下:

void InitializeContext(v8::Isolate* isolate, v8::Local<v8::Context> context) {
  v8::HandleScope handle_scope(isolate);
  v8::Context::Scope context_scope(context);

  auto global = context->Global();

  auto deno_val = v8::Object::New(isolate);
  CHECK(global->Set(context, deno::v8_str("libdeno"), deno_val).FromJust());

  auto print_tmpl = v8::FunctionTemplate::New(isolate, Print);
  auto print_val = print_tmpl->GetFunction(context).ToLocalChecked();
  CHECK(deno_val->Set(context, deno::v8_str("print"), print_val).FromJust());

  auto recv_tmpl = v8::FunctionTemplate::New(isolate, Recv);
  auto recv_val = recv_tmpl->GetFunction(context).ToLocalChecked();
  CHECK(deno_val->Set(context, deno::v8_str("recv"), recv_val).FromJust());

  auto send_tmpl = v8::FunctionTemplate::New(isolate, Send);
  auto send_val = send_tmpl->GetFunction(context).ToLocalChecked();
  CHECK(deno_val->Set(context, deno::v8_str("send"), send_val).FromJust());

  auto eval_context_tmpl = v8::FunctionTemplate::New(isolate, EvalContext);
  auto eval_context_val =
      eval_context_tmpl->GetFunction(context).ToLocalChecked();
  CHECK(deno_val->Set(context, deno::v8_str("evalContext"), eval_context_val)
            .FromJust());

  auto error_to_json_tmpl = v8::FunctionTemplate::New(isolate, ErrorToJSON);
  auto error_to_json_val =
      error_to_json_tmpl->GetFunction(context).ToLocalChecked();
  CHECK(deno_val->Set(context, deno::v8_str("errorToJSON"), error_to_json_val)
            .FromJust());

  CHECK(deno_val->SetAccessor(context, deno::v8_str("shared"), Shared)
            .FromJust());
}

在完成綁定之后,在Typescript中可以通過如下代碼實(shí)現(xiàn)c++方法和Typescript方法的映射

libdeno.ts
interface Libdeno {
  recv(cb: MessageCallback): void;

  send(control: ArrayBufferView, data?: ArrayBufferView): null | Uint8Array;

  print(x: string, isErr?: boolean): void;

  shared: ArrayBuffer;

  /** Evaluate provided code in the current context.
   * It differs from eval(...) in that it does not create a new context.
   * Returns an array: [output, errInfo].
   * If an error occurs, `output` becomes null and `errInfo` is non-null.
   */
  // eslint-disable-next-line @typescript-eslint/no-explicit-any
  evalContext(code: string): [any, EvalErrorInfo | null];

  errorToJSON: (e: Error) => string;
}

export const libdeno = window.libdeno as Libdeno;

在執(zhí)行Typescript代碼時,只需要引入libdeno,就直接調(diào)用c++方法,例如:

import { libdeno } from "./libdeno";
function sendInternal(
  builder: flatbuffers.Builder,
  innerType: msg.Any,
  inner: flatbuffers.Offset,
  data: undefined | ArrayBufferView,
  sync = true
): [number, null | Uint8Array] {
  const cmdId = nextCmdId++;
  msg.Base.startBase(builder);
  msg.Base.addInner(builder, inner);
  msg.Base.addInnerType(builder, innerType);
  msg.Base.addSync(builder, sync);
  msg.Base.addCmdId(builder, cmdId);
  builder.finish(msg.Base.endBase(builder));
  const res = libdeno.send(builder.asUint8Array(), data);
  builder.inUse = false;
  return [cmdId, res];
}

調(diào)用libdeno.send方法可以將數(shù)據(jù)傳給c++,然后通過c++去調(diào)用rust代碼實(shí)現(xiàn)具體的工程操作。

Typescript層同步異步實(shí)現(xiàn)

同步

在Typescript中只需要設(shè)置sendInternal方法的sync參數(shù)為true即可,在rust中會根據(jù)sync參數(shù)去判斷是執(zhí)行同步或者異步操作,如果sync為true,libdeono.send方法會返回執(zhí)行的結(jié)果,rust和typescript之間傳遞數(shù)據(jù)需要將數(shù)據(jù)序列化,這里序列化操作使用的是flatbuffer庫。

const [cmdId, resBuf] = sendInternal(builder, innerType, inner, data, true);
異步實(shí)現(xiàn)

同理,實(shí)現(xiàn)異步方式,只需要設(shè)置sync參數(shù)為false即可,但是異步操作和同步相比,多了回掉方法,在執(zhí)行異步通信時,libdeno.send方法會返回一個唯一的cmdId標(biāo)志這次調(diào)用操作。同時在異步通信完成后,會創(chuàng)建一個promise對象,將cmdId作為key,promise作為value,加入map中。代碼如下:

const [cmdId, resBuf] = sendInternal(builder, innerType, inner, data, false);
  util.assert(resBuf == null);
  const promise = util.createResolvable<msg.Base>();
  promiseTable.set(cmdId, promise);
  return promise;

rust實(shí)現(xiàn)同步和異步

當(dāng)在Typescript中調(diào)用libdeno.send方法時,調(diào)用了C++文件binding.cc中的Send方法,該方法是在deno初始化時綁定到v8 isolate上去的。在Send方法中去調(diào)用了ops.rs文件中的dispatch方法,該方法實(shí)現(xiàn)了消息到函數(shù)的映射。每個類型的消息對應(yīng)了一種函數(shù),例如讀文件消息對應(yīng)了讀文件的函數(shù)。

pub fn dispatch(
  isolate: &Isolate,
  control: libdeno::deno_buf,
  data: libdeno::deno_buf,
) -> (bool, Box<Op>) {
  let base = msg::get_root_as_base(&control);
  let is_sync = base.sync();
  let inner_type = base.inner_type();
  let cmd_id = base.cmd_id();

  let op: Box<Op> = if inner_type == msg::Any::SetTimeout {
    // SetTimeout is an exceptional op: the global timeout field is part of the
    // Isolate state (not the IsolateState state) and it must be updated on the
    // main thread.
    assert_eq!(is_sync, true);
    op_set_timeout(isolate, &base, data)
  } else {
    // Handle regular ops.
    let op_creator: OpCreator = match inner_type {
      msg::Any::Accept => op_accept,
      msg::Any::Chdir => op_chdir,
      msg::Any::Chmod => op_chmod,
      msg::Any::Close => op_close,
      msg::Any::FetchModuleMetaData => op_fetch_module_meta_data,
      msg::Any::CopyFile => op_copy_file,
      msg::Any::Cwd => op_cwd,
      msg::Any::Dial => op_dial,
      msg::Any::Environ => op_env,
      msg::Any::Exit => op_exit,
      msg::Any::Fetch => op_fetch,
      msg::Any::FormatError => op_format_error,
      msg::Any::Listen => op_listen,
      msg::Any::MakeTempDir => op_make_temp_dir,
      msg::Any::Metrics => op_metrics,
      msg::Any::Mkdir => op_mkdir,
      msg::Any::Open => op_open,
      msg::Any::ReadDir => op_read_dir,
      msg::Any::ReadFile => op_read_file,
      msg::Any::Readlink => op_read_link,
      msg::Any::Read => op_read,
      msg::Any::Remove => op_remove,
      msg::Any::Rename => op_rename,
      msg::Any::ReplReadline => op_repl_readline,
      msg::Any::ReplStart => op_repl_start,
      msg::Any::Resources => op_resources,
      msg::Any::Run => op_run,
      msg::Any::RunStatus => op_run_status,
      msg::Any::SetEnv => op_set_env,
      msg::Any::Shutdown => op_shutdown,
      msg::Any::Start => op_start,
      msg::Any::Stat => op_stat,
      msg::Any::Symlink => op_symlink,
      msg::Any::Truncate => op_truncate,
      msg::Any::WorkerGetMessage => op_worker_get_message,
      msg::Any::WorkerPostMessage => op_worker_post_message,
      msg::Any::Write => op_write,
      msg::Any::WriteFile => op_write_file,
      msg::Any::Now => op_now,
      msg::Any::IsTTY => op_is_tty,
      msg::Any::Seek => op_seek,
      msg::Any::Permissions => op_permissions,
      msg::Any::PermissionRevoke => op_revoke_permission,
      _ => panic!(format!(
        "Unhandled message {}",
        msg::enum_name_any(inner_type)
      )),
    };
    op_creator(&isolate, &base, data)
  };

  // ...省略多余的代碼
}

在每個類型的函數(shù)中會根據(jù)在Typescript中調(diào)用libdeo.send方法時傳入的sync參數(shù)值去判斷同步執(zhí)行還是異步執(zhí)行。

let (is_sync, op) = dispatch(isolate, control_buf, zero_copy_buf);
同步執(zhí)行

在執(zhí)行dispatch方法后,會返回is_sync的變量,如果is_sync為true,表示該方法是同步執(zhí)行的,op表示返回的結(jié)果。rust代碼會調(diào)用c++文件api.cc中的deno_respond方法,將執(zhí)行結(jié)果同步回去,deno_respond方法中根據(jù)current_args_的值去判斷是否為同步消息,如果current_args_存在值,則直接返回結(jié)果。

異步執(zhí)行

在deno中,執(zhí)行異步操作是通過rust的Tokio模塊來實(shí)現(xiàn)的,在調(diào)用dispatch方法后,如果是異步操作,is_sync的值為false,op不再是執(zhí)行結(jié)果,而是一個執(zhí)行函數(shù)。通過tokio模塊派生一個線程程異步去執(zhí)行該函數(shù)。

    let task = op
      .and_then(move |buf| {
        let sender = tx; // tx is moved to new thread
        sender.send((zero_copy_id, buf)).expect("tx.send error");
        Ok(())
      }).map_err(|_| ());
    tokio::spawn(task);

在deno初始化時,會創(chuàng)建一個管道,代碼如下:

let (tx, rx) = mpsc::channel::<(usize, Buf)>();

管道可以實(shí)現(xiàn)不同線程之間的通信,由于異步操作是創(chuàng)建了一個新的線程去執(zhí)行的,所以子線程無法直接和主線程之間通信,需要通過管道的機(jī)制去實(shí)現(xiàn)。在異步代碼執(zhí)行完成后,調(diào)用tx.send方法將執(zhí)行結(jié)果加入管道里面,event loop會每次從管道里面去讀取結(jié)果返回回去。

Event Loop

由于異步操作依賴事件循環(huán),所以先解釋一下deno中的事件循環(huán),其實(shí)事件循環(huán)很簡單,就是一段循環(huán)執(zhí)行的代碼,當(dāng)達(dá)到條件后,事件循環(huán)會結(jié)束執(zhí)行,deno中主要的事件循環(huán)代碼實(shí)現(xiàn)如下:

pub fn event_loop(&self) -> Result<(), JSError> {
    // Main thread event loop.
    while !self.is_idle() {
      match recv_deadline(&self.rx, self.get_timeout_due()) {
        Ok((zero_copy_id, buf)) => self.complete_op(zero_copy_id, buf),
        Err(mpsc::RecvTimeoutError::Timeout) => self.timeout(),
        Err(e) => panic!("recv_deadline() failed: {:?}", e),
      }
      self.check_promise_errors();
      if let Some(err) = self.last_exception() {
        return Err(err);
      }
    }
    // Check on done
    self.check_promise_errors();
    if let Some(err) = self.last_exception() {
      return Err(err);
    }
    Ok(())
  }

self.is_idle方法用來判斷是否所有的異步操作都執(zhí)行完畢,當(dāng)所有的異步操作都執(zhí)行完畢后,停止事件循環(huán),is_idle方法代碼如下:

fn is_idle(&self) -> bool {
    self.ntasks.get() == 0 && self.get_timeout_due().is_none()
  }

當(dāng)產(chǎn)生一次異步方法調(diào)用時,會調(diào)用下面的方法,使ntasks內(nèi)部的值加1,

fn ntasks_increment(&self) {
    assert!(self.ntasks.get() >= 0);
    self.ntasks.set(self.ntasks.get() + 1);
  }

在event loop循環(huán)中,每次從管道中去取值,這里event loop充消費(fèi)者,執(zhí)行異步方法的子線程充當(dāng)生產(chǎn)者。如果在一次事件循環(huán)中,獲取到了一次執(zhí)行結(jié)果,那么會調(diào)用ntasks_decrement方法,使ntasks內(nèi)部的值減1,當(dāng)ntasks的值為0的時候,事件循環(huán)會退出執(zhí)行。在每次循環(huán)中,將管道中取得的值作為參數(shù),調(diào)用complete_op方法,將結(jié)果返回回去。

rust中將異步操作結(jié)果返回回去

在初始化v8實(shí)例時,綁定的c++方法中有一個Recv方法,該方法的作用時暴露一個Typescript的函數(shù)給rust,在deno的io.ts文件的start方法中執(zhí)行l(wèi)ibdeno.recv(handleAsyncMsgFromRust),將handleAsyncMsgFromRust函數(shù)通過c++方法暴露給rust。具體實(shí)現(xiàn)如下:

export function start(source?: string): msg.StartRes {
  libdeno.recv(handleAsyncMsgFromRust);

  // First we send an empty `Start` message to let the privileged side know we
  // are ready. The response should be a `StartRes` message containing the CLI
  // args and other info.
  const startResMsg = sendStart();

  util.setLogDebug(startResMsg.debugFlag(), source);

  setGlobals(startResMsg.pid(), startResMsg.noColor(), startResMsg.execPath()!);

  return startResMsg;
}

當(dāng)異步操作執(zhí)行完成后,可以在rust中直接調(diào)用handleAsyncMsgFromRust方法,將結(jié)果返回給Typescript。先看一下handleAsyncMsgFromRust方法的實(shí)現(xiàn)細(xì)節(jié):

export function handleAsyncMsgFromRust(ui8: Uint8Array): void {
  // If a the buffer is empty, recv() on the native side timed out and we
  // did not receive a message.
  if (ui8 && ui8.length) {
    const bb = new flatbuffers.ByteBuffer(ui8);
    const base = msg.Base.getRootAsBase(bb);
    const cmdId = base.cmdId();
    const promise = promiseTable.get(cmdId);
    util.assert(promise != null, `Expecting promise in table. ${cmdId}`);
    promiseTable.delete(cmdId);
    const err = errors.maybeError(base);
    if (err != null) {
      promise!.reject(err);
    } else {
      promise!.resolve(base);
    }
  }
  // Fire timers that have become runnable.
  fireTimers();
}

從代碼handleAsyncMsgFromRust方法的實(shí)現(xiàn)中可以知道,首先通過flatbuffer反序列化返回的結(jié)果,然后獲取返回結(jié)果的cmdId,根據(jù)cmdId獲取之前創(chuàng)建的promise對象,然后調(diào)用promise.resolve方法觸發(fā)promise.then中的代碼執(zhí)行。

關(guān)于實(shí)現(xiàn)deno通信的方法就分享到這里了,希望以上內(nèi)容可以對大家有一定的幫助,可以學(xué)到更多知識。如果覺得文章不錯,可以把它分享出去讓更多的人看到。

向AI問一下細(xì)節(jié)

免責(zé)聲明:本站發(fā)布的內(nèi)容(圖片、視頻和文字)以原創(chuàng)、轉(zhuǎn)載和分享為主,文章觀點(diǎn)不代表本網(wǎng)站立場,如果涉及侵權(quán)請聯(lián)系站長郵箱:is@yisu.com進(jìn)行舉報,并提供相關(guān)證據(jù),一經(jīng)查實(shí),將立刻刪除涉嫌侵權(quán)內(nèi)容。

AI