Server-Sent Events "channel" where all messages are broadcasted to all connected clients, history is maintained automatically and server attempts to keep clients alive by sending "keep-alive" packets automatically.
We shouldn't use flush() blindly. We need it in the case where the compression middleware has been added, for instance, but by default it'll trigger deprecation warnings from node. Not sure how to fix this, perhaps it's possible to get hold of the native flush method and do a strict equality check?
We shouldn't use
flush()blindly. We need it in the case where thecompressionmiddleware has been added, for instance, but by default it'll trigger deprecation warnings from node. Not sure how to fix this, perhaps it's possible to get hold of the nativeflushmethod and do a strict equality check?