[ye]

150ms latency should be fine for almost anything that's not an FPS game.

Systems like onLive are capable of bringing high-end graphics to low powered devices like tablets, netbooks, and notebooks, phones even.

And keep in mind that 150ms will reduce as our technology gets better and more servers get deployed.

[lcedp]

I don't know. Working with shell is very uncomfy with 170 ms ping. (I use mosh which prints typed symbols right away not waiting for response from server, but other feedback such as commands output or cursor movement is still very unpleasant at that lag).

[riskable]

I agree with this. That's why I spent so much time optimizing Gate One's Terminal->HTML encoder. On my i7 laptop the round-trip time for keystroke->screen update hovers around 10-20ms on localhost (remember though: My laptop is processing both ends at the same time).

On actual server hardware that "baseline latency" is about 5-10ms. So for any given client connecting to Gate One the response time for keystrokes should be at most 10ms + whatever the connection latency is.

[lcedp]

I'm positively impressed with responsiveness of this html project, but 170 ms in my case is the shear distance to the server :)