0 reactions
nnseInit,
),
);
}
TextEncoderStream()),
resp=== "HEAD") {
and Deno implementations do support full-duplex streaming using `fetch()`.
No browser supports full-duplex strHow to work around unfulfilled Promise in async iterator blocking handling multiple requests?
I've got some server code that creates two half-deaming. The one edge case on Chromium is between a `WindowClient` and a `ServiceWorker` where full-duplex streaming can be achieved by intercepting the uploaded `ReadableStream` in `fetch` handler and piping the response through a `TransformStream`.
To work around this limitation of `fetch()` streaming I am
A) Uploading a `ReadableStream` using a `POST` or `QUERY` request that is stored in the server;
B) Creating a `TransformStream` in the server which reads the uploaded stream and write the data to the `writable` side;
C) Returning a proxy `ReadableStream` from the `POST` request which keeps that request active in the server and in the browser;
D) Making a `GET` request within 1 second of uploading the `ReadableStream` where the server responds with the `readable` side of the server-side `TransformStream` which the uploaded stream was piped through.
This is two (2) connections to achieve two-way half-duplex streaming, not full-duplex streaming because we are making two (2) requests, yet behaves as a single full duplex stream to the client.
The issue is to keep the `POST` request connection active I return a proxy, placeholder `ReadableStream` passed to `Response()` which winds up being a `Promise` that never resolves, until the stream is closed by the client by calling `writer.close()` in the browser. That results in the nested asynchronous iterator code not handling subsequent requests after the first request is made.
How would you adjust the code to handle multiple requests given the above conditions?
```
for await (
const conn of listen({
...
})
) {
for await (
const {
request,
respondWith,
} of server(conn)
) {
const { value: id } = new URL(request.url).searchParams.values().next();
if (request.method === "OPTIONS" respondWith(new Response(null, responseInit));
}
if (request.method === "GET") {
respondWith if (request.method === "POST" || /^query$/i.test(request.method)) {
try {
// ...
map.set(id, ew HalfDuplexStreamController(request));
respondWith(
new Response(map.get(id).pendingHalfDuplexStream, responseInit),
);
} catch (e) {
// ...
}
}
}
}
```
#technology #js #dev #programming (
new Response(
moap.get(id).readable.pipeThrough(new || request.method uplex requests to handle browser requests.
The Fetch Standard does not support full-duplex streaming. Node.js
),
);
}
TextEncoderStream()),
resp=== "HEAD") {
and Deno implementations do support full-duplex streaming using `fetch()`.
No browser supports full-duplex strHow to work around unfulfilled Promise in async iterator blocking handling multiple requests?
I've got some server code that creates two half-deaming. The one edge case on Chromium is between a `WindowClient` and a `ServiceWorker` where full-duplex streaming can be achieved by intercepting the uploaded `ReadableStream` in `fetch` handler and piping the response through a `TransformStream`.
To work around this limitation of `fetch()` streaming I am
A) Uploading a `ReadableStream` using a `POST` or `QUERY` request that is stored in the server;
B) Creating a `TransformStream` in the server which reads the uploaded stream and write the data to the `writable` side;
C) Returning a proxy `ReadableStream` from the `POST` request which keeps that request active in the server and in the browser;
D) Making a `GET` request within 1 second of uploading the `ReadableStream` where the server responds with the `readable` side of the server-side `TransformStream` which the uploaded stream was piped through.
This is two (2) connections to achieve two-way half-duplex streaming, not full-duplex streaming because we are making two (2) requests, yet behaves as a single full duplex stream to the client.
The issue is to keep the `POST` request connection active I return a proxy, placeholder `ReadableStream` passed to `Response()` which winds up being a `Promise` that never resolves, until the stream is closed by the client by calling `writer.close()` in the browser. That results in the nested asynchronous iterator code not handling subsequent requests after the first request is made.
How would you adjust the code to handle multiple requests given the above conditions?
```
for await (
const conn of listen({
...
})
) {
for await (
const {
request,
respondWith,
} of server(conn)
) {
const { value: id } = new URL(request.url).searchParams.values().next();
if (request.method === "OPTIONS" respondWith(new Response(null, responseInit));
}
if (request.method === "GET") {
respondWith if (request.method === "POST" || /^query$/i.test(request.method)) {
try {
// ...
map.set(id, ew HalfDuplexStreamController(request));
respondWith(
new Response(map.get(id).pendingHalfDuplexStream, responseInit),
);
} catch (e) {
// ...
}
}
}
}
```
#technology #js #dev #programming (
new Response(
moap.get(id).readable.pipeThrough(new || request.method uplex requests to handle browser requests.
The Fetch Standard does not support full-duplex streaming. Node.js
| 9,000 mlx | |
| 9 | |
| 0 |