|
|
|
|
|
by MichaelGG
4407 days ago
|
|
>I'm fairly sure this is not the web that Tim Berners-Lee envisioned. So? None of these are convincing arguments for application developers. Having to rewrite an application to perform all its UI logic on the server side in addition to client side is a lot of work, for almost no benefit to the people paying to make the application. As a user, so long URLs work so I can send locations to other people, then most of my accessibility scenarios are solved. The rest is simply a lack of technology in other clients. |
|
When you receive a GET request for an URL, and the browser tells you it accepts text/html, it is expected that you answer with the content stored at that URL in the format requested. It is not expected that you answer with an application that when run will eventually produce the content.
The correct way to do what this post is saying is to create a new mime type for this content delivery method. Then, if the browser actively tells you it accepts that content type, deliver it.
What the OP proposes is not text/html. It's something else.