js-libp2p-mplex

JavaScript implementation of mplex.

Install
npm install @libp2p/mplex
Usage
import { Mplex } from '@libp2p/mplex'
import { pipe } from 'it-pipe'
const muxer = new Mplex({
onStream: stream => {
},
onStreamEnd: stream => {
}
})
pipe(conn, muxer, conn)
const stream = muxer.newStream()
pipe([1, 2, 3], stream)
API
const muxer = new Mplex([options])
Create a new duplex stream that can be piped together with a connection in order to allow multiplexed communications.
e.g.
import { Mplex } from '@libp2p/mplex'
import { pipe } from 'it-pipe'
const muxer = new Mplex()
pipe(conn, muxer, conn)
options is an optional Object that may have the following properties:
onStream - A function called when receiving a new stream from the remote. e.g.
const onStream = stream => {
pipe(
stream,
source => (async function * () {
for await (const data of source) yield data
})(),
stream
)
}
const muxer = new Mplex({ onStream })
Note: The onStream function can be passed in place of the options object. i.e.
new Mplex(stream => { })
onStreamEnd - A function called when a stream ends
const onStreamEnd = stream => {
}
const muxer = new Mplex({ onStreamEnd })
signal - An AbortSignal which can be used to abort the muxer, including all of it's multiplexed connections. e.g.
const controller = new AbortController()
const muxer = new Mplex({ signal: controller.signal })
pipe(conn, muxer, conn)
controller.abort()
maxMsgSize - The maximum size in bytes the data field of multiplexed messages may contain (default 1MB)
muxer.onStream
Use this property as an alternative to passing onStream as an option to the Mplex constructor.
muxer.onStreamEnd
Use this property as an alternative to passing onStreamEnd as an option to the Mplex constructor.
muxer.streams
Returns an Array of streams that are currently open. Closed streams will not be returned.
const stream = muxer.newStream([options])
Initiate a new stream with the remote. Returns a duplex stream.
e.g.
const stream = muxer.newStream()
pipe([1, 2, 3], stream, consume)
In addition to sink and source properties, this stream also has the following API, that will normally not be used by stream consumers.
stream.close()
Closes the stream for reading. If iterating over the source of this stream in a for await of loop, it will return (exit the loop) after any buffered data has been consumed.
This function is called automatically by the muxer when it receives a CLOSE message from the remote.
The source will return normally, the sink will continue to consume.
stream.abort([err])
Closes the stream for reading and writing. This should be called when a local error has occurred.
Note, if called without an error any buffered data in the source can still be consumed and the stream will end normally.
This will cause a RESET message to be sent to the remote, unless the sink has already ended.
The sink will return and the source will throw if an error is passed or return normally if not.
stream.reset()
Closes the stream immediately for reading and writing. This should be called when a remote error has occurred.
This function is called automatically by the muxer when it receives a RESET message from the remote.
The sink will return and the source will throw.
stream.timeline
Returns an object with close and open times of the stream.
stream.id
Returns a string with an identifier unique to this muxer. Identifiers are not unique across muxers.
Contribute
The libp2p implementation in JavaScript is a work in progress. As such, there are a few things you can do right now to help out:
- Go through the modules and check out existing issues. This is especially useful for modules in active development. Some knowledge of IPFS/libp2p may be required, as well as the infrastructure behind it - for instance, you may need to read up on p2p and more complex operations like muxing to be able to help technically.
- Perform code reviews. More eyes will help a) speed the project along b) ensure quality and c) reduce possible future bugs.
License
Licensed under either of
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.