astraw/bui-backend

backend server for Browser User Interface (BUI)

bui-backend's Issues

Disallow failures on nightly

FYI, cargo-web 0.4.2 is building again on the newest nightly, so you can revert commit d2ca064. (:

Some questions before I decide if I port my frontend to bui

This project looks very interesting, but before I switch my existing frontend over to bui I have some questions:

1. Why does it use server-sent events instead of websockets? When will it be possible to use websockets instead?
2. How flexible is it, does it impose any restrictions on what the frontend can do? Or can it be a full featured web app that uses webgl, canvas, svg, localstorage etc.?
3. When to use bui instead of just writing a frontend in yew and backend with (rocket|rouille|hyper) + ws-rs (and then injecting the ws port into the page before serving, if the port is dynamic) or actix (to serve websockets on the same port)?
4. Will it ever support something like browser-sync, to reload all clients when the source changes (maybe using the notify crate like cargo-watch)?

My current project uses a frontend written in polymer, I'm using browser-sync to auto-reload the app when the files change on disk, but I want to rewrite the frontend in Rust with yew (for wasm) so that I can re-use code and types from my backend and get static type safety.
My server side uses ws-rs and I want to keep using websockets because somewhere I've read that they have lower latency than server-sent events, is that true?
Btw, this project is a DJing/VJing application and needs the lowest possible latency.