workers-help
pages-help
general-help
durable-objects
workers-and-pages-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
⚡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd-runtime
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows
vite-plugin
pipelines-beta
containers-beta
Build Chat interface
CVEs
https://developers.cloudflare.com/
I see that the worker websocket is

You can use the `transactionSync()`
transactionSync()
https://developers.cloudflare.com/durable-objects/api/storage-api/#transactionsync if you want to control when the writes happen.
The error handling is not as clear cut though. You might need to handle the error in your worker calling the DO to make sure all exceptions are caught during that DO transaction. Using the above method guarantees that you won't have partial writes....with sveltekit i cannot (yet) directly
Hm weird no clue then havent tried any
i just realized this could be used as a
When you do `acceptWebsocket()`, you can
acceptWebsocket()
, you can include a topic string Param after the socket param, then you can get only sockets associated with a topic when doing getWebSockets(topic)
Why can't your client make many connections? WebSockets are relatively low overhead for the frontend when they aren't actively received data...Im interested in using DO for my chat
> We did some rough maths and it’s gonna
We did some rough maths and it’s gonna take 37 days to do soWhat is the math you did? We cannot help otherwise....
Storage Ops when connecting to DO Hibernatable Websockets

Looking for thoughts on the following
Hey team 👋 , I am having issues with
Error: Durable Object is overloaded. Requests queued for too long.
.The document says An individual Object has a soft limit of 1,000 requests per second.
is there a setting or configuration which can be set to increase this limit?If your client is in the browser this
@quan @1984 Ford Laser It was definitely
Okay this is a dumb one, I think I fixed
message
and close
WS handlers, I also had a error
one set up, which was supposed to remove the current connection from the list of connections, but wasn't necessarily closing the connection, such as if the client experienced an error, but not one that caused the socket to close. Somewhere, this was causing the socket to stay open or something. You can see a comparison in the screenshots
Anyone else having issues with