Retry limit on connection

[sampk2004]

This is related to this issue that is related to this pr, and this issue. I have a use case where I want to keep the sse connected in the background even when messages are not coming in. I realized the retry limit is not being replenished upon successful connection and a message has to come in for it to be reset. Is there any advice on how to handle the retries in this case?

[sampk2004]

Any updates on this?

[enisdenjo]

Sorry for the delay on this one, it got lost in my GH notifications. There is actually a reason why the retry counter is reset only after receiving events, and it's documented here:

graphql-sse/src/client.ts

Lines 551 to 558 in 918b9d4

	for await (const result of getResults()) {
	// only after receiving results are future connects not considered retries.
	// this is because a client might successfully connect, but the server
	// ends up terminating the connection afterwards before streaming anything.
	// of course, if the client completes the subscription, this loop will
	// break and therefore stop the stream (it wont reconnect)
	retryingErr = null;
	retries = 0;

Maybe we could have an option or something that would change this behaviour? Do you have any suggestions? A PR is very welcome though!

[sampk2004]

Thank you for the reply, I will try to make a pr when I find time!