Expose SSE retry time updates via the public API

[jamesmissen]

Issue #5471 was closed with the recommendation to reconnect to SSE streams in the application layer.

It would be helpful to expose the retry times in retry fields from the event stream, so that any reconnection attempts in a higher layer could respect the latest retry time if desired.

Currently, the retry times are parsed but they remain in the internal API only, terminating here:

okhttp/okhttp-sse/src/main/kotlin/okhttp3/sse/internal/RealEventSource.kt

Lines 127 to 129 in 75b9c26

	override fun onRetryChange(timeMs: Long) {
	// Ignored. We do not auto-retry.
	}

[yschimke]

Yep, this seems like a valid part of the API. Exposed in other frameworks like https://github.com/spring-projects/spring-framework/blob/main/spring-web/src/main/java/org/springframework/http/codec/ServerSentEvent.java

And as you say, web EventSource implements retry observing that. https://html.spec.whatwg.org/multipage/server-sent-events.html#event-stream-interpretation

@swankjesse @JakeWharton any objection to exposing? It would allow building a correct retrying implementation on top.

[JakeWharton]

Let's expose. We don't support automatic retry so we need to surface this to the caller.

[ricardomgarciaf]

Has there been any update regarding this? It'd be very useful to have this field exposed.

[JakeWharton]

No updates