Improving Rocket example

[maacl]

Ref this example

If I understand correctly a new EventStream is created every time the delay signal changes. Is there an interest in a patch that avoids this?

[GlenDC]

I would do this as a 2nd example that could be based on the hello example or can also be something more realistic.

Your assumption is correct, and can be easily seen with the developer tools in your browser. Normally you want to have a Long-Lived connection for stuff like this where you stream all your events, but to do this properly adds immediately a lot of extra code which might be a bit intimidating for a very simple hello-world example. You'll see that this "one-shot" connection is what all datastar hello world examples do, I imagine for this reason.

Happy to accept a PR where you add a more realistic example though. E.g. you can see a more realistic example I made and maintain for the rama datastar module: https://github.com/plabayo/rama/blob/main/examples/http_sse_datastar_hello.rs ; but as you can see once you want to go a bit more realistic things start to get a lot more complex very quickly. Such complexity is of course a small price to pay within an actual useful product / backend. But it can be seen as "complex" or "too much" in a toy example where that price might not be easily justified. If you get what I mean.

But happy to accept a PR where such an example for the Rocket or Axum framework (or both) is done though, very welcome for sure. I would however keep the hello-world example minimal and simple. Except for perhaps adding a note to there about the fact that it is a toy example and that usually you want to have X and Y (e.g. persistent long-lived connections), and then refer to the new example you (or someone else) would add.

[GlenDC]

Closed in #3 by @maacl