Great insight @User thank you so much

Hmm, am I not able to clearInterval a timer? The error I get from the DO is: Cannot clear a timeout created in a different request context.

Really odd

Yep. You have to emulate Intervals with repeated

setTimeouts

. You can't clear those either but you can gate them. I made a little helper for that: https://gist.github.com/codefrau/cd7d25ee88f034c71bba9cf6ba51f9b7

... and I sure hope this will be fixed before GA 😅 I reported it back in May https://discord.com/channels/595317990191398933/773219443911819284/847724822984261633

Hmm I see, do you know why this is happening though? Is it because the timer was created in context from another user

I think for some reason DOs still retain the idea that resources should be separated by request. That makes sense for regular worker requests but not for DOs, because the whole point of a DO is to serve many requests.

Yeah that makes sense, and hopefully it'll be fixed 🙂

I'm running game session logic with setTimeouts, e.g. how long someone can draw per round

It's just a bug, but likely deep down in the architecture. @User ? @User ? Any news?

Your fix seems nice, so you basically cancel the timeout so it doesn't fire the callback function if it's cancelled.

Right. Pretty straightforward. And once Cloudflare fixes the 10,000 timeout limit it can easily be used to implement intervals. (I have not checked that one lately)

Yeah, thank you so much for the fix and quick response! 🙂

there is a fix in the works, just held up in code reviews which is mostly my fault (as the overly-strict reviewer)

Both for the "cannot clear" error and "too many timeouts" ?

@User is there any problem with your fix if I use a global var for the timer? E.g. this.roundTimer = setTimeout(...) and then later in another user context the timer might get replaced with a new one.

So basically in my pictionary, if someone finds the correct word, the round timer is changed to 20 seconds, from whatever it was before 🙂

Of course I clear it before replacing: if (this.roundTimer) { clearTimeout(this.roundTimer) } this.roundTimer = setTimeout(() => { this.endRound() }, 10000)

you shouldn't be using globals because global state is sometimes shared between DO instances.

Ah hmm by global I mean (this) as in the reference inside the DO

(this) within the class

oh yes that is fine, that is how I use it

Ok great!

Is there a way to dispose/kill a DO instance?

E.g. if everyone leaves a room

if you delete everything from the DO then it will be cleaned up and removed

Does

{cf: {cacheTtl: 3600}}

work on requests to durable objects?

Is there a limit on how large a websocket message can be?

And can I guarantee that websocket messages sent from DO to user are received in same order

No, the cache isn't between a normal Worker and a Durable Object like it is between a normal Worker and origin. You'd need to make a client side wrapper around your DO fetches that uses the Cache API and fell back to fetching from the DO