I can imagine using websocket would be
I can imagine using websocket would be more efficient. We built our previous chat API entirely over HTTP requests and polling, similar analogy. I can't speak to the specifics on a theoretically implementation using DOs as you have described.
In production our current use-case necessitated we create a new client ws connection per DO. I don't see how using RPC between DOs would reasonably or efficiently solve the issue.
1 Reply
In production our current use-case necessitated we create a new client ws connection per DO. I don't see how using RPC between DOs would reasonably or efficiently solve the issue.Please explain. Maybe I'm missing something. Why can't you have one WebSocket connection from the browser to a single DO, then host your other state in other DOs?