Yeah

I imagine that can be raised?

>>> Unless otherwise negotiated as a part of an enterprise level contract, …

So yeah

ah lmao thanks

Anyone know if it's possible to establish a websocket between two durable objects?

It is

How do you create the client side without a URL?

You give it a random one. DOs don’t need a specific hostname to work

You can call it https://google.com for all it cares

The client web socket api doesn’t produce a request object, there’s nothing to pass to the fetch method of the stub.

When you receive a Response, you can pull a WebSocket out of it

That’s using a request generated by a browser, I’m asking about establishing a connection between two durable objects.

It’s either not possible, or maybe there’s an alternate method to initiate sockets in a DO, or there’s a way to extract a remote DO URI from the stub, but I have read the available docs and public code examples and it’s not clear to me how to accomplish this.

That example is for the worker side of things

Unless I’m missing something, that example has a socket request originating in a web client with a DO endpoint. “In client-side JavaScript, connect to your Workers function using WebSockets:”

Look at the "​​Writing a WebSocket client" section?

Ah, got it, thank you everybody.

Hey guys, have a problem with durable objects appearing as

undefined

. Here is my code:

js
    let id = req.env.rooms.idFromName("index");
    console.log(id)
    console.log(req.env.rooms.get(id))

which prints the following:

js
DurableObjectId {
  name: undefined
}
DurableObject {
  name: undefined,
  id: undefined
}

this is my class:

js
export class Chatroom {
    constructor(controller, env) {
        console.log("constructing new object")
        this.storage = controller.storage;
        this.env = env;
        this.sessions = [];
        this.lastTimestamp = 0;
    }

    async fetch(req) {
        console.log("fetch")
        if (req.headers.get("Upgrade") !== "websocket") {
            return json("Expected upgrade", 426)
        }

        const ws = new WebSocketPair();
        const [client, server] = Object.values(ws);

        await this.handleSession(server)

        return new Response(null, {
            status: 101,
            webSocket: client
        });
    }

    async handleSession(ws) {
        console.log("made it here")
        ws.accept();

        ws.addEventListener("message", async msg => {
            ws.send(msg.data)
        })
    }
}

and my bindings:

toml
[durable_objects]
bindings = [
  { name = "rooms", class_name = "Chatroom" }
]

[[migrations]]
tag = "v1" # Should be unique for each entry
new_classes = ["Chatroom"]

Would appreciate any pointers!

To be clear, the specific error is:

js
/Users/bigballs/rizzle/backend/node_modules/wrangler/wrangler-dist/cli.js:27100
            throw ex;
            ^

Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -54,
  code: 'ECONNRESET',
  syscall: 'read'
}

Morning all, I have a requirement that if the DO code is changed, then a job needs to run when the update is pushed. Anyone got any patterns for this?

Are you doing anything after the "console.log(req.env.rooms.get(id))"

Have a deployment ID in the DO class that changes automatically on deploy, and then run an alarm every minute(more or less), see if it changed as compared to the stored deployment ID. If so, run the job

Don't I need to do something to set an alarm? i.e. if no request is sent to the DO, then there is no way the alarm can be set.

When you initially create it, yes, but after that, the alarm handler can call itself