SSE vs Websocket

SSE

https://html.spec.whatwg.org/multipage/server-sent-events.html

https://web.dev/articles/eventsource-basics?hl=ja

Legacy proxy servers are known to, in certain cases, drop HTTP connections after a short timeout. To protect against such proxy servers, authors can include a comment line (one starting with a ':' character) every 15 seconds or so.

It is better to include a unique identifier in the document when it is served and then pass that identifier as part of the URL when the connection is established.

Clients that support HTTP's per-server connection limitation might run into trouble when opening multiple pages from a site if each page has an EventSource to the same domain. Authors can avoid this using the relatively complex mechanism of using unique domain names per connection, or by allowing the user to enable or disable the EventSource functionality on a per-page basis, or by sharing a single EventSource object using a shared worker.

ブラウザで 6 つ以上の接続ができるか検証

websocket も？

push proxy

https://web.dev/articles/eventsource-basics?hl=ja#server-sent_events_versus_websockets

セキュリティ

https://web.dev/articles/websockets-basics?hl=ja

https://www.timeplus.com/post/websocket-vs-sse

https://stackoverflow.com/questions/63583989/performance-difference-between-websocket-and-server-sent-events-sse-for-chat-r