4 ms·
Does the article's author realize that the HTTP's request-response model wasn't some technology limitation of old times, but conscious and pretty sensible desig
by romaniv 15y ago
Does the article's author realize that the HTTP's request-response model wasn't some technology limitation of old times, but conscious and pretty sensible design that led to current popularity of the web? Here is what it allowed:
- URIs, i.e. ability to connect all the documents on the Web.
- Standardized UIs that are easy to create.
- Security. You don't need to execute unknown code to load a page, yet you can use web interfaces to do a lot of different things.
- Control an transparency for the users. Browser is your software, you decide what it will and won't do.
With the increased used of heavy JS clients, most of these benefits are fading away.
- joshowens 15y agoI would disagree, the article never said do away with server side security or anything like that. I don't think it said anything about ditching URIs either.
- icebraining 15y agoSecurity is for the client. And ditching URIs is often a direct consequence of using AJAX to load the document dynamically, since the current URL doesn't represent the current document anymore.