Security News
JSR Working Group Kicks Off with Ambitious Roadmap and Plans for Open Governance
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
@hyperswarm/rpc
Advanced tools
Simple RPC over the Hyperswarm DHT, backed by Protomux.
npm install @hyperswarm/rpc
const RPC = require('@hyperswarm/rpc')
const rpc = new RPC()
const server = rpc.createServer()
await server.listen()
server.respond('echo', (req) => req)
const client = rpc.connect(server.publicKey)
await client.request('echo', Buffer.from('hello world'))
// <Buffer 'hello world'>
const rpc = new RPC([options])
Construct a new RPC instance.
Options include:
{
// Optional default value encoding.
valueEncoding: encoding,
// A Noise keypair that will be used by default to listen/connect on the DHT.
// Defaults to a new key pair.
keyPair,
// A unique, 32-byte, random seed that can be used to deterministically
// generate the key pair.
seed: buffer,
// Optionally overwrite the default bootstrap servers. Not used if a DHT
// instance is passed instead.
bootstrap: ['host:port'],
// A DHT instance. Defaults to a new instance.
dht
}
await rpc.destroy([options])
Fully destroy this RPC instance.
This will also close any running servers. If you want to force close the instance without waiting for the servers to close pass { force: true }
.
const client = rpc.connect(publicKey[, options])
Options are the same as dht.connect()
.
const response = await client.request(method, value[, options])
Perform an RPC request, returning a promise that will resolve with the value returned by the request handler or reject with an error.
Options include:
{
// Optional encoding for both requests and responses, defaults to raw
valueEncoding: encoding,
requestEncoding: encoding, // Optional encoding for requests
responseEncoding: encoding // Optional encoding for responses
}
client.event(method, value[, options])
Perform an RPC request but don't wait for a response.
Options are the same as client.request()
.
client.cork()
Cork the underlying channel. See channel.cork()
for more information.
client.uncork()
Uncork the underlying channel. See channel.uncork()
for more information.
await client.end()
Gracefully end the RPC channel, waiting for all inflights requests before closing.
client.destroy([err])
Forcefully close the RPC channel, rejecting any inflight requests.
client.on('open', [handshake])
Emitted when the remote side adds the RPC protocol.
client.on('close')
Emitted when the RPC channel closes, i.e. when the remote side closes or rejects the RPC protocol or we closed it.
client.on('destroy')
Emitted when the RPC channel is destroyed, i.e. after close
when all pending promises has resolved.
const server = rpc.createServer([options])
Create a new RPC server for responding to requests.
Options are the same as dht.createServer()
.
await server.listen([keyPair])
Make the server listen on a key pair, defaulting to rpc.defaultKeyPair
. To connect to this server use keyPair.publicKey
as the connect address.
server.respond(method[, options], handler)
Register a handler for an RPC method. The handler is passed the request value and must either return the response value or throw an error.
Only a single handler may be active for any given method; any previous handler is overwritten when registering a new one.
Options include:
{
// Optional encoding for both requests and responses, defaults to raw
valueEncoding: encoding,
requestEncoding: encoding, // Optional encoding for requests
responseEncoding: encoding // Optional encoding for responses
}
server.unrespond(method)
Remove a handler for an RPC method.
await server.close()
Stop listening.
server.address()
Returns an object containing the address of the server:
{
host, // External IP of the server,
port, // External port of the server if predictable,
publicKey // Public key of the server
}
server.on('listening')
Emitted when the server is fully listening on a key pair.
server.on('close')
Emitted when the server is fully closed.
ISC
FAQs
RPC over the Hyperswarm DHT
The npm package @hyperswarm/rpc receives a total of 175 weekly downloads. As such, @hyperswarm/rpc popularity was classified as not popular.
We found that @hyperswarm/rpc demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.