Slashdot Mirror


Smarter Clients Via ReverseHTTP and WebSockets

igrigorik writes "Most web applications are built with the assumption that the client / browser is 'dumb,' which places all the scalability requirements and load on the server. We've built a number of crutches in the form of Cache headers, ETags, and accelerators, but none has fundamentally solved the problem. As a thought experiment: what if the browser also contained a Web server? A look at some of the emerging trends and solutions: HTML 5 WebSocket API and ReverseHTTP."

3 of 235 comments (clear)

  1. Is this a follow-up to the previous story? by gatekeep · · Score: 3, Funny

    This seems to closely relate to the next story currently on the frontpage; Predicting Malicious Web Attacks

  2. Re:Problem? by ceoyoyo · · Score: 5, Funny

    Ah, but the young 'uns have forgotten that anybody did anything before they came along. So "the network" is synonymous with "the web" and if you want to send any information it better be over HTTP. So bidirectional HTTP means you can communicate in both directions!

    Next they're going to figure out that if you move the web app out of the browser you can have a much richer GUI experience.

  3. Re:Problem? by Tablizer · · Score: 2, Funny

    What? There were computers before 1985?

    Yes, but they were disguised as mere keyboards to fool you toddlers.