Limited availability
Secure context: This feature is available only in secure contexts (HTTPS), in some or all supporting browsers.
Note: This feature is available in Web Workers.
The createUnidirectionalStream() method of the WebTransport interface asynchronously opens a unidirectional stream.
The method returns a Promise that resolves to a WritableStream object, which can be used to reliably write data to the server.
"Reliable" means that transmission and order of data are guaranteed. This provides slower delivery (albeit faster than with WebSockets) than datagrams, but is needed in situations where reliability and ordering are important, like chat applications.
The relative order in which queued bytes are emptied from created streams can be specified using the sendOrder option. If set, queued bytes in streams with a higher send order are guaranteed to be sent before queued bytes for streams with a lower send order. If the order number is not set then the order in which bytes are sent is implementation dependent. Note however that even though bytes from higher send-order streams are sent first, they may not arrive first.
createUnidirectionalStream()
createUnidirectionalStream(options)
options Optional
An object that may have the following properties:
sendOrder Optional
A integer value specifying the send priority of this stream relative to other streams for which the value has been set. Queued bytes are sent first for streams that have a higher value. If not set, the send order depends on the implementation.
A Promise that resolves to a WebTransportSendStream object (this is a WritableStream).
InvalidStateError DOMException
Thrown if createUnidirectionalStream() is invoked while the WebTransport is closed or failed.
Use the createUnidirectionalStream() method to get a reference to a WritableStream. From this you can get a writer to allow data to be written to the stream and sent to the server.
Use the close() method of the resulting WritableStreamDefaultWriter to close the associated HTTP/3 connection. The browser tries to send all pending data before actually closing the associated connection.
async function writeData() {
const stream = await transport.createUnidirectionalStream({
sendOrder: "596996858",
});
const writer = stream.getWriter();
const data1 = new Uint8Array([65, 66, 67]);
const data2 = new Uint8Array([68, 69, 70]);
writer.write(data1);
writer.write(data2);
try {
await writer.close();
console.log("All data has been sent.");
} catch (error) {
console.error(`An error occurred: ${error}`);
}
}
You can also use WritableStreamDefaultWriter.abort() to abruptly terminate the stream. When using abort(), the browser may discard any pending data that hasn't yet been sent.
// â¦
const stream = await transport.createUnidirectionalStream();
const writer = stream.getWriter();
// â¦
writer.write(data1);
writer.write(data2);
await writer.abort();
// Not all the data may have been written.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4