3 ms·

I'm not sure I'm following you. How does this differ from native EventSource?

• supermatt 11y ago
  EventSource sends all events over a single connection which it keeps open indefinitely. This shim receives a single event and then reconnects. In that window there is a period where there will be no connection to send events over, so they will be lost without a queue. Edit: actually this looks to be a lot more sophisticated than the other shims i havr looked at and does indeed behave more like eventsource. Good job!
  • qubyte 11y ago
    Ah, you're suggesting that the shims use long-polling. I don't think that's the case though. If I understand the library correctly, it really is keeping a connection open, so it's really very similar to the way EventSource works. Addition: Verified. It doesn't disconnect between events (not long-polling).
• deleted 11y ago
  [deleted]