onConnectionClosed firing multiple times and connecting more than once (server restart)

[philstrong]

onConnectionClosed is called for connection close and end.

connect is called twice
the first connect makes a request but before it can get a response
the 2nd connect is called. In both states readyState is CONNECTING
the 2nd connect makes a request
the first connect now gets a response and is connected
the 2nd connect now gets a response and is connected

restart the server again (we now get 4 connects) and this perpetuates.

[philstrong]

I merged this in my fork but still needs consideration for aslakhellesoy/eventsource

[elado]

👍

[lanwin]

Is there a reason why this still isnt merged?

[aslakhellesoy]

The reaon @lanwin is that I tend to prioritise paid work (this is not). I prioritise open source work when I need it myself, or if I happen to be in the right mood, with some spare time.

Thanks for the reminder though.

[yinzer]

With 57,090 downloads in the last day one would think something like this might get a little more attention

[tobilg]

Thanks @aslakhellesoy for your work on this project. I think @yinzer is kind of correct. I also see the double-reconnect behavior (there are two "real" connections instead of one) once the SSE server is restarted.

This can be more or less a showstopper for this module IMO.

[philstrong]

open source is hard! ;p