hpvd

thats interesting! Would reallly interesting what about the numbers in full real world example appliccation.

just a another deep link: 8) Consuming a fetch as a stream https://developer.mozilla.org/en-US/docs/Web/API/Streams_API/Using_readable_streams#consuming_a_fetch_as_a_stream

fetch examples consisting of live demos and its source code have been moved to: https://github.com/mdn/dom-examples/tree/master/fetch Link to Demos: https://github.com/mdn/dom-examples/tree/master/fetch#fetch-examples

What do you think of this example? https://mdn.github.io/dom-examples/fetch/fetch-text/ Isn't this the direction we are looking for (to sent requests up)? (in combination with using SSE to directly push messages down...

added some more detail into comment above

or am I constantly thinking into a complete wrong direction with this - `fetch` to sent a requests up and - `SSE` to push something directly down ? And this...

when clicking around, typical **real world speed** is - varying between 3ms and 26ms, - with average of **16ms** - which is 60Hz refresh rate Distance to cover from browser...

glad to see you are looking into details further! just two questions regarding speed: 1) this is quite a big difference in speed in your benchmark between websocket and fetch....

regarding the question: what is fast enough? we had to first answer the question: fast enough for what? 1. for a multiplayer game? Then we should be end to end...

when thinking about "fast enough for which use case?"... If we agree with the done [benchmark](https://github.com/beenotung/ts-liveview/issues/13#issuecomment-1221289037) that - there is no distortion in the comparison (see 2 questions from https://github.com/beenotung/ts-liveview/issues/13#issuecomment-1221321472)...