> In that case a reconnect logic would be necessary. But same applies to websockets. Arguably you’re even better off in the SSE case, because it specifies a re

> In that case a reconnect logic would be necessary. But same applies to websockets. Arguably you’re even better off in the SSE case, because it specifies a reconnect mechanism that allows clients to reconnect without receiving duplicate data. If you’re working with a client library that understands this (which includes any to-spec browser-based client), you just need to handle the reconnect header on the server and you get reconnects for “free”.