Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You can replace HTTP with anything you want using WebSockets, but I never got what's wrong with it.


Given that websockets don't even work reliably yet, and are not even implemented in all popular browsers of the day, that's hardly a proposition. Not to mention that everybody implementing his own HTTP replacement from scratch with websockets instead of a common standard is a highway to hell.

As for what's wrong with it:

- better support for non-blocking requests - better support for streaming media - better support for caching - better content negotiation (e.g for "retina" x2 assets) - better authentication mechanisms - better support for encryption

Also check: http://static.usenix.org/event/usenix99/invited_talks/mogul....




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: