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?
1 Reply
For that matter, are websockets going to work in a pages _worker.js ? I know not all features work in pages