2 A request is needed to create a WebSocket connection. There is no charge for outgoing WebSocket messages, nor for incoming WebSocket protocol pings ↗.

2 A request is needed to create a WebSocket connection. There is no charge for outgoing WebSocket messages, nor for incoming WebSocket protocol pings ↗.

5.5.2.  Ping

   The Ping frame contains an opcode of 0x9.

   A Ping frame MAY include "Application data".

   Upon receipt of a Ping frame, an endpoint MUST send a Pong frame in
   response, unless it already received a Close frame.  It SHOULD
   respond with Pong frame as soon as is practical.  Pong frames are
   discussed in Section 5.5.3.

   An endpoint MAY send a Ping frame any time after the connection is
   established and before the connection is closed.

   NOTE: A Ping frame may serve either as a keepalive or as a means to
   verify that the remote endpoint is still responsive.

5.5.3.  Pong

   The Pong frame contains an opcode of 0xA.

   Section 5.5.2 details requirements that apply to both Ping and Pong
   frames.

   A Pong frame sent in response to a Ping frame must have identical
   "Application data" as found in the message body of the Ping frame
   being replied to.

   If an endpoint receives a Ping frame and has not yet sent Pong
   frame(s) in response to previous Ping frame(s), the endpoint MAY
   elect to send a Pong frame for only the most recently processed Ping
   frame.

5.5.2.  Ping

   The Ping frame contains an opcode of 0x9.

   A Ping frame MAY include "Application data".

   Upon receipt of a Ping frame, an endpoint MUST send a Pong frame in
   response, unless it already received a Close frame.  It SHOULD
   respond with Pong frame as soon as is practical.  Pong frames are
   discussed in Section 5.5.3.

   An endpoint MAY send a Ping frame any time after the connection is
   established and before the connection is closed.

   NOTE: A Ping frame may serve either as a keepalive or as a means to
   verify that the remote endpoint is still responsive.

5.5.3.  Pong

   The Pong frame contains an opcode of 0xA.

   Section 5.5.2 details requirements that apply to both Ping and Pong
   frames.

   A Pong frame sent in response to a Ping frame must have identical
   "Application data" as found in the message body of the Ping frame
   being replied to.

   If an endpoint receives a Ping frame and has not yet sent Pong
   frame(s) in response to previous Ping frame(s), the endpoint MAY
   elect to send a Pong frame for only the most recently processed Ping
   frame.

const app = new Hono()

app.get('/websocket', async ({ req, env }) => {
    const id = req.param('id');
    const notifierId = env.WEBSOCKET_NOTIFIER.idFromName(id);
    const notifier = env.WEBSOCKET_NOTIFIER.get(id);
    return notifier.fetch(req.url, req);
});


export class WebsocketNotifier extends DurableObject<Env> {
    sessions = new Set<WebSocket>();

    async fetch(request: Request) {
        if (request.headers.get('Upgrade') != 'websocket') {
            return new Response('expected websocket', { status: 400 });
        }

        const pair = new WebSocketPair();

        // We're going to take pair[1] as our end, and return pair[0] to the client.
        await this.handleSession(pair[1]);

        // Now we return the other end of the pair to the client.
        return new Response(null, { status: 101, webSocket: pair[0] });
    }

    // handleSession() implements our WebSocket-based chat protocol.
    async handleSession(webSocket: WebSocket) {
        // Accept our end of the WebSocket. This tells the runtime that we'll be terminating the
        // WebSocket in JavaScript, not sending it elsewhere.
        this.state.acceptWebSocket(webSocket);

        this.sessions.add(webSocket);

        let storage = await this.storage.list<Record<any, any>>({ reverse: true, limit: 100 });
        let backlog = [...storage.values()];
        backlog.reverse();
        backlog.forEach((value) => {
            webSocket.send(JSON.stringify(value));
        });
    }
 ...
}

const app = new Hono()

app.get('/websocket', async ({ req, env }) => {
    const id = req.param('id');
    const notifierId = env.WEBSOCKET_NOTIFIER.idFromName(id);
    const notifier = env.WEBSOCKET_NOTIFIER.get(id);
    return notifier.fetch(req.url, req);
});


export class WebsocketNotifier extends DurableObject<Env> {
    sessions = new Set<WebSocket>();

    async fetch(request: Request) {
        if (request.headers.get('Upgrade') != 'websocket') {
            return new Response('expected websocket', { status: 400 });
        }

        const pair = new WebSocketPair();

        // We're going to take pair[1] as our end, and return pair[0] to the client.
        await this.handleSession(pair[1]);

        // Now we return the other end of the pair to the client.
        return new Response(null, { status: 101, webSocket: pair[0] });
    }

    // handleSession() implements our WebSocket-based chat protocol.
    async handleSession(webSocket: WebSocket) {
        // Accept our end of the WebSocket. This tells the runtime that we'll be terminating the
        // WebSocket in JavaScript, not sending it elsewhere.
        this.state.acceptWebSocket(webSocket);

        this.sessions.add(webSocket);

        let storage = await this.storage.list<Record<any, any>>({ reverse: true, limit: 100 });
        let backlog = [...storage.values()];
        backlog.reverse();
        backlog.forEach((value) => {
            webSocket.send(JSON.stringify(value));
        });
    }
 ...
}

const startedAt = Date.now()
await env.MY_QUEUE.send({ foo: "bar"})
console.info("took", Date.now() - startedAt)

const startedAt = Date.now()
await env.MY_QUEUE.send({ foo: "bar"})
console.info("took", Date.now() - startedAt)