seems the websockets from durableobjects dont negotiate it

sending to a websocket is not working for me if the request that calls websocket.send originated from a POST request, could that be right?

a POST request into a durable object triggers a broadcast

(if that cant be right it might be some other bug i got)

ah

it seems a crash inside a function in a DO does not report error in all cases

trying to reference an undefined does not report any errors

state = {tmp: {limit: 50}} state.tmp.jobs.length <<< this does not throw, silently fails with no error

yup ignore that above about the POST, it was a mistake on my part that DOs do not throw under

i'm trying to delete a durable object with

wrangler publish --delete-class Counter

but I get this error:

"code": 10061,
  "message": "Cannot create binding for class Counter because it is not currently configured to implement durable objects. Did you forget to apply a --new-class migration to it?"

(wrangler version

1.15.0-custom-builds-rc.2

with repo: https://github.com/cloudflare/durable-objects-template) any thoughts?

Thanks for this super detailed explanation! 🙂

@User As you proposed I tried to get the

request.cf

value directly at the eyeball request, but it seems it's not available there as well. I created a minimal example based on the

durable-objects-rollup-esm

template to reproduce this: https://gist.github.com/nightvisi0n/48c4844a0a81103c31c5071383889cda (I stripped away everything related to DO for simplicity)

Curious to know answers to these! I'd like to build a similar thing but in my mind I am treating a "room" as a durable object instance, and in that case 128mb of memory is quite generous.

looks like a couple of my questions around websockets were answered in a docs last night https://github.com/cloudflare/cloudflare-docs/blob/production/products/workers/src/content/learning/using-websockets.md

a neat trick here is you can pass authentication/initial messages as 2nd param in form of list

so 1 step handshake vs 3 way

the docs create a WebSocket like this:

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

any particular reason it's not just this?

const [client, server] = new WebSocketPair()

i think cuz the pair is [0] and [1]

so the keys would be numeric

webSocketPair = {0: client, 1: server}

oh i see you used square brackets, does ES6 understand taht and automagically take the values?

regardless thats very confusing code to look at, since youl assume WebSocketPair is a list after 3 months revisiting your code

i don't see any sense in having

WebSocketPair

return a non-iterable with numeric keys.

Let's say I have a DO for each user but I also have a DO for a game they are playing. Are two different websocket connections recommended for the client? Or one websocket connection to the user DO and the game sends w.e websocket messages to the users DO?

imagine if you had to do this with React hooks:

const state = useState(0)
const [count, setCount] = Object.values(state)

i think its a minor detail regardless wonder if theres a reason for using a object vs a list

it's needlessly unergonomic.

cloudflare folks, consider adding this to the WebsocketPair class:

js
  *[Symbol.iterator]() {
    yield* Object.values(this)
  }

then destructuring will work without the

Object.values

call.