Add WebSockets documentation using our MVP template code examples as reference
Questions from users:
- Socket timeouts, how does it handle reconnect? Is that the job of the client or can the server reconnect in a permanent listen mode?
- Can the server only listen for clients? Can the websocket service connect to anything else (ie. a notification service to receive events?)
- I'm assuming you setup a page to "answer" the websocket - what are the limitations if any? I assume I can run everything I can in a page including liquid?
- Timeouts for the page, is the page considered a background task? When receiving information will the process timeout like a page (I'm assuming not - see next point)
- EOL (end of line) or packets - sockets are just a stream of data, how do you define a message, start and stop of data, types of data etc?
- Parallel processing, assuming just one connection, but how does the server keep up if there are streams of events one after another, does it split off thread / processes in the background to cover this or queue this somehow? Websockets are not just a "post" of data but stream so want to know how things are handled.
Add WebSockets documentation using our MVP template code examples as reference
Questions from users: