https://github.com/MetaMask/json-rpc-middleware-stream/blob/master/test/index.js#L20

A small toolset for streaming json rpc and matching requests and responses. Made to be used with json-rpc-engine.

可以用来与json-rpc-engine结合使用的,对输入的json rpc进行读入、写出处理

json-rpc-middleware-stream/index.js

const SafeEventEmitter = require('safe-event-emitter')
const DuplexStream = require('readable-stream').Duplex //即一个可读且可写的流 module.exports = createStreamMiddleware function createStreamMiddleware() {
const idMap = {}
const stream = new DuplexStream({
objectMode: true, //输入的是任意形式的数据,而不非是字符串和 Buffer(或 Uint8Array
read: readNoop, //下面定义的返回false的函数,会覆写_read(),当要从别地流处读出时调用
write: processMessage,//会覆写_write(),当要写入别的流时调用
}) const events = new SafeEventEmitter() const middleware = (req, res, next, end) => {
// write req to stream
stream.push(req)//从req流中读出,就会去调用readNoop函数
// register request on id map
idMap[req.id] = { req, res, next, end }//并在数组中将req根据其id记录下来
} return { events, middleware, stream } function readNoop () {
return false
} function processMessage (res, encoding, cb) {//当要写出时调用
let err
try {
const isNotification = !res.id //如果res.id有值,则isNotification为false;否则为true
if (isNotification) {//res.id没值或为0
processNotification(res)//触发事件'notification'
} else {
processResponse(res)//res.id有值
}
} catch (_err) {
err = _err
}
// continue processing stream
cb(err)
} function processResponse(res) {//将流中内容写出到res流
const context = idMap[res.id] //查看有没有与相应的res.id相同的ID的流之前读入过
if (!context) throw new Error(`StreamMiddleware - Unknown response id ${res.id}`) //如果context为空,则说明相应的id的流并没有读入过,这样写出的时候就不知道要怎么写出了,无end,所以会出错
delete idMap[res.id] //如果有读入过,则写出前先清空idMap中的相应内容
// copy whole res onto original res
Object.assign(context.res, res) //然后将现在要写出到的res流覆写context.res,并返回context.res
// run callback on empty stack,
// prevent internal stream-handler from catching errors
setTimeout(context.end) //调用之前读入时写好的end函数来结束写出操作
} function processNotification(res) {//该事件的监听会在inpage-provider处设置
events.emit('notification', res)
} }
Object.assign(target, ...sources):用于将所有可枚举属性的值从一个或多个源对象复制到目标对象。它将返回目标对象。

json-rpc-middleware-stream/engineStream.js

const DuplexStream = require('readable-stream').Duplex

module.exports = createEngineStream

function createEngineStream({ engine }) {//engine即RpcEngine
if (!engine) throw new Error('Missing engine parameter!')
const stream = new DuplexStream({ objectMode: true, read, write })
// forward notifications
if (engine.on) {
engine.on('notification', (message) => {//监听'notification'事件
stream.push(message) //事件被触发的话就将message数据读入stream,调用read函数
})
}
return stream function read () {
return false
}
function write (req, encoding, cb) {//当写出时调用该函数
engine.handle(req, (err, res) => {
this.push(res)
})
cb()
}
}

测试:

json-rpc-middleware-stream/test/index.js

const test = require('tape')
const RpcEngine = require('json-rpc-engine')
const createJsonRpcStream = require('../index')
const createEngineStream = require('../engineStream') test('middleware - raw test', (t) => { const jsonRpcConnection = createJsonRpcStream()
const req = { id: , jsonrpc: '2.0', method: 'test' }
const initRes = { id: , jsonrpc: '2.0' }
const res = { id: , jsonrpc: '2.0', result: 'test' } // listen for incomming requests
jsonRpcConnection.stream.on('data', (_req) => {//监听data事件
t.equal(req, _req, 'got the expected request')//说明触发data事件传来的
jsonRpcConnection.stream.write(res)//将流中的与res.id相同的数据写出
}) // run middleware, expect end fn to be called
jsonRpcConnection.middleware(req, initRes, () => {//将req流写入createJsonRpcStream
t.fail('should not call next')
}, (err) => {
t.notOk(err, 'should not error')
t.deepEqual(initRes, res, 'got the expected response')
t.end()
}) }) test('engine to stream - raw test', (t) => { const engine = new RpcEngine()
engine.push((req, res, next, end) => {
res.result = 'test'
end()
}) const stream = createEngineStream({ engine })
const req = { id: , jsonrpc: '2.0', method: 'test' }
const res = { id: , jsonrpc: '2.0', result: 'test' } // listen for incomming requests
stream.on('data', (_res) => {
t.deepEqual(res, _res, 'got the expected response')
t.end()
}) stream.on('error', (err) => {
t.fail(error.message)
}) stream.write(req) }) test('middleware and engine to stream', (t) => {//上面两者的结合 // create guest
const engineA = new RpcEngine()
const jsonRpcConnection = createJsonRpcStream()
engineA.push(jsonRpcConnection.middleware) // create host
const engineB = new RpcEngine()
engineB.push((req, res, next, end) => {
res.result = 'test'
end()
}) // connect both
const clientSideStream = jsonRpcConnection.stream
const hostSideStream = createEngineStream({ engine: engineB })
clientSideStream
.pipe(hostSideStream)
.pipe(clientSideStream) // request and expected result
const req = { id: , jsonrpc: '2.0', method: 'test' }
const res = { id: , jsonrpc: '2.0', result: 'test' } engineA.handle(req, (err, _res) => {//req调用jsonRpcConnection.middleware读入clientSideStream,然后hostSideStream从clientSideStream中读入req数据,然后调用engineB的方法写出,所以得到的result: 'test'
t.notOk(err, 'does not error')
t.deepEqual(res, _res, 'got the expected response')
t.end()
}) }) test('server notification', (t) => {
t.plan() const jsonRpcConnection = createJsonRpcStream()
const notif = { jsonrpc: '2.0', method: 'test_notif' }//这里没有设置id,所以调用write所以会触发processNotification函数,触发'notification'事件 jsonRpcConnection.events.once('notification', (message) => {
t.equals(message.method, notif.method)
t.end()
}) // receive notification
jsonRpcConnection.stream.write(notif)
}) test('server notification in stream', (t) => {
const engine = new RpcEngine() const stream = createEngineStream({ engine })
const notif = { jsonrpc: '2.0', method: 'test_notif' } // listen for incomming requests
stream.once('data', (_notif) => {
t.deepEqual(notif, _notif, 'got the expected notification')
t.end()
}) stream.on('error', (err) => {
t.fail(error.message)
}) engine.emit('notification', notif)//将触发createEngineStream中的'notification'事件,notif将被读入stream,将触发data事件
})

MetaMask/json-rpc-middleware-stream的更多相关文章

  1. 測试JSON RPC远程调用(JSONclient)

    #include <string> #include <iostream> #include <curl/curl.h> /* 标题:JSonclient Auth ...

  2. MetaMask/metamask-inpage-provider

    https://github.com/MetaMask/metamask-inpage-provider Used to initialize the inpage ethereum provider ...

  3. metamask源码学习-metamask-controller.js

    The MetaMask Controller——The central metamask controller. Aggregates other controllers and exports a ...

  4. metamask源码学习-inpage.js

    The most confusing part about porting MetaMask to a new platform is the way we provide the Web3 API ...

  5. Guide to Porting MetaMask to a New Environment

    https://github.com/MetaMask/metamask-extension/blob/develop/docs/porting_to_new_environment.md MetaM ...

  6. 【.NET Core项目实战-统一认证平台】第十六章 网关篇-Ocelot集成RPC服务

    [.NET Core项目实战-统一认证平台]开篇及目录索引 一.什么是RPC RPC是"远程调用(Remote Procedure Call)"的一个名称的缩写,并不是任何规范化的 ...

  7. metamask源码学习-contentscript.js

    When a new site is visited, the WebExtension creates a new ContentScript in that page's context, whi ...

  8. MetaMask/json-rpc-engine

    https://github.com/MetaMask/json-rpc-engine RpcEngine——MetaMask/json-rpc-engine https://github.com/M ...

  9. 以太坊RPC机制与API实例

    上一篇文章介绍了以太坊的基础知识,我们了解了web3.js的调用方式是通过以太坊RPC技术,本篇文章旨在研究如何开发.编译.运行与使用以太坊RPC接口. 关键字:以太坊,RPC,JSON-RPC,cl ...

随机推荐

  1. DotNetty项目基本了解和介绍

    一.DotNetty背景介绍 DotNetty是微软的Azure团队,使用C#实现的Netty的版本发布.不但使用了C#和.Net平台的技术特点,并且保留了Netty原来绝大部分的编程接口.让我们在使 ...

  2. vue按需引入element或mint

    vue按需引入element或mint需要添加 babel-preset-es2015 和babel-plugin-component

  3. C code example for strdup

    #include <stdlib.h> #include <stdio.h> #include <string.h> #include <malloc.h&g ...

  4. C#多线程——同步

    多个线程(不仅仅局限于相同进程)如果需要访问相同的可变资源的话就可能需要考虑到线程同步的手段.CPU的线程和进程管控我这里就不去说了,计算机组成原理里面的东西 那么既然要让线程的步调一致,那么我们首先 ...

  5. canvas-4fillstyle.html

    fillStyle color gradient pattern image canvas video strokeStyle

  6. extract-text-webpack-plugin 作用、安装、使用

    作用:该插件的主要是为了抽离css样式,防止将样式打包在js中引起页面样式加载错乱的现象 安装:插件安装命令如下: npm install extract-text-webpack-plugin -- ...

  7. ExtJS学习之MessageBox

    MessageBox为ExtJS中的消息对话框,包括alert  confirm prompt show四种. 1.index.html <!DOCTYPE html PUBLIC " ...

  8. maven 技巧

    M2Eclipse Releases maven eclipse插件最新安装地址 Full Version Tag 1.0 2011-06-22 http://download.eclipse.org ...

  9. Android之ProgressDialog的使用

    ProgressDialog 继承自AlertDialog,AlertDialog继承自Dialog,实现DialogInterface接口. ProgressDialog的创建方式有两种,一种是ne ...

  10. 【Java入门提高篇】Day21 Java容器类详解(四)ArrayList源码分析

    今天要介绍的是List接口中最常用的实现类——ArrayList,本篇的源码分析基于JDK8,如果有不一致的地方,可先切换到JDK8后再进行操作. 本篇的内容主要包括这几块: 1.源码结构介绍 2.源 ...