hey, I've been struggling with my stuff (DO's calling each other's via stubs). I also witnessed issues with websockets just dying. All of these are random and more or less frequent over the minutes. I'm implementing retry mechanisms everywhere and ping/pong over the websockets. But even then, I can get periods where 3 DO's going down and not responding at any fetch() requests for tens of seconds once every hour or so. I get this is a private beta, but i'm getting to a point where stuff becomes too unreliable for wanting to build anything with for now. I'd be glad to get more insights on potential network/server load issues being worked on atm, because I had a much more stable experience last week than this week. 🙂

(websockets are for additional non-DO's connections)

Any changes that would start blocking websockets? 🤔

I just noticed that websocket connections are failing right away, with no changes on our side (at least I am not aware of any), anyone else can confirm?

Hello everyone, we are building on cloudflare and really need durable objects to launch (just message passing, losing data / beta grade is 100% AOK), already applied for beta access 4-6 months ago. No reply yet, I was wondering if it was possible to make a compelling usecase for it and hopefully get the green light sooner.

dang no metadata like on KV storage? its so useful for our previews so we dont need to readback the full value

DO list actually returns the values as well, so you can skip the metadata part

is there a timelimit on websocket connections? or they can even stay open hours?

also would opening a websocket connection from inside a durable object to another endpoint ever be supported?

@User I don't know of any changes that would have had any effect on websockets today

I'm glad to hear your excitement about using DO; we're working hard to move into open beta soon (as @User has mentioned) and we're excited to hear your feedback when it does launch - stay tuned for updates 🙂

Possible to know how soon is soon? Like if soon is not soon we need to make the decision to write a bunch of code that we will thrown into a fire pit once Durable Objects does open to beta. Like is soon is soon enough, we wont allocate resources to that.

how does one use environment variables in a durable object

https://developers.cloudflare.com/workers/runtime-apis/durable-objects#durable-object-class-definition tldr;

...
constructor(state, env) {
  this.env = env
}
...
this.env.ENV_OR_SECRET
...

it is indeed right there 🤦‍♂️ I seem to be unable to edit it in the UI so that threw me. success via wrangler, thanks!

Seems like Workers are somehow not respecting the

Upgrade

header (and doing the magic) anymore 🤔 Or is it possible I reached websocket connections limit?

It just started working.. no changes on my side, but I tried to upgrade my Cloudflare plan.. so either something on your side or I was indeed somehow rate-limited on websockets connections.. 😅

whats the limit for websockets on basic / free plan vs higher plan?

I don't believe there is any official limit... see this: https://community.cloudflare.com/t/cloudflare-websocket-limits/57455

wowq tyway more then i need on free tier

I have been able to open a websocket to another DO. Note that any connection initiated inside a DO would still be subject to the request context and DO appear to have the same subrequest limits as a regular worker.

1 message off the websocket is a subrequest?

Interesting, if the dns is on cloudflare, it might be possible then to open the websocket to it, even if it's not a worker/do?

I think one websocket connection counts as a single subrequest.

oh thats lovely then, so much potential im very excited

wish cloudflare woudl give me closed beta access 💢

https://blog.ceru.dev/websockets-at-the-edge/ check out the very last bit of this post

did not realize you can fool a browser client into turning a fetch into a websocket conection

Nah it's only for Workers

Afaik