Slashdot Mirror

← Back to Stories (view on slashdot.org)

Smarter Clients Via ReverseHTTP and WebSockets

Posted by kdawson on from the edges-are-not-dumb dept.

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."

1 of 235 comments (clear)

  1. Re:Connection, yes. Server, no. by Scootin159 · · Score: 3, Interesting

    While I agree with the parent, that accepting incoming connections is a bad thing - it may also be the "killer feature" to implement IPv6. Auto-configuring clients to support incoming connections is inherently difficult in NAT.