No documentation for oneshot vs streaming difference and capabilities #5
Description
Hello! I just found out about this an hour ago and my first confusion was around the mention of oneshot vs streaming response concepts, but there's no explanation on the difference other other than it's streaming or not.
My assumption is that you can simply keep the connection alive and keep streaming elements back to the client as needed? Can you stream the same element over and over to support live-updates? Is there any concept of having to split those at all, since in practice a non-SSE stream doesn't really have those, or does it purely rely on timing? A quick look at the code seems to suggest the latter.
This is a really cool project BTW, and I'm most likely going to try it out since I'm already writing a bunch of wrappers around my experimental datastar app.
Edit: I'm also curious about how open you'd be to have some kind of SSE support added to the non-core library if it can provide a safer, more consistent way to stream changes back instead of relying on timing luck (if that's indeed what's happening here)