Is a Durable Object necessary to retain a server WebSocket?
My application establishes a web socket with the client, and then uses it to send a message when another application hits a worker. It's a pages app.
Ideally, I'd like to avoid a durable object so I can deploy the whole thing using pages git route.
My application needs to maintain a reference to the web socket, after the function that has created it has returned. Do I need to create a durable object to hold that reference, or is there some other way?
Ideally, I'd like to avoid a durable object so I can deploy the whole thing using pages git route.
My application needs to maintain a reference to the web socket, after the function that has created it has returned. Do I need to create a durable object to hold that reference, or is there some other way?
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,801Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
