Split off streaming (Event Iterator SSE) from Client Retry

[divmgl]

Hey! Just wanted to say that oRPC is a seriously impressive project and my team has also struggled quite a bit with tRPC and OpenAPI. Such a shame that this was not available when we picked tRPC, but at least tRPC inspired this project!

I'm experimenting with a prototype on my spare time and it makes heavy use of SSE. I was surprised to go through the oRPC documentation and see it supports this out of the box!

https://orpc.unnoq.com/docs/plugins/client-retry

I think this deserves its own page, especially given that it's not really related to the retry mechanism.

Thanks for your hard work on this!

[unnoq]

Why it not really related to the retry mechanism?

The oRPC event‑iterator is a general-purpose tool, not tied to SSE (but follow SSE spec). If you instead implement an infinite retry loop, it behaves like a “true” SSE connection (It can stop simply by returning from the iterator)

[divmgl]

Interesting! Okay I'll give it a shot today and maybe I'll understand it better!

[unnoq]

Did you review it yet, Any improvement needed?

[Axedyson]

@unnoq

Wait just to understand oRPC's SSE implementation doesn't use native web SSE under the hood?

Right now by default browser limit SSE to 6-10 concurrent connections I think. But if oRPC doesn't use this natively then it is unlimited?

[unnoq]

@Axedyson yes, oRPC uses native 'fetch' steaming response.

[divmgl]

@unnoq I've been using SSE with no problems, thank you!

[unnoq]

I think this discussion is resolved. I will close it - feel free to reopen it if you'd like.