"Paul L"
Does such a beast exist or am I entirely day dreaming?
Daydreaming, at least partly: Just consider state that can't be stored client-side at all, e.g. the contents of a wiki page. Networking or HTML as interface isn't the real problem: It's the multi-headedness of applications that make things complicated. As soon as you have multiple programs or multiple instances of the same program modify shared data, things get involved. Traffic is another problem if state accumulates. Thinking about REST, a nice feature to have would be session timeout notifying: The server can keep the connection open and replace the displayed page with one notifying the user that he's too slow for current timeout settings. -- (c) this sig last receiving data processing entity. Inspect headers for past copyright information. All rights reserved. Unauthorised copying, hiring, renting, public performance and/or broadcasting of this signature prohibited.