Think....
A web service (or maybe just a ASP page) renders and serves an XML generated based on the inputs passed to it.
A web browser picks it up, uses XSLT to transform it into a lovely page.
And what do you get, an application which does not waste too much time on the server.
Do not speak, just think.....Does nt your mind do a full revolution???
Anyway my friend really sparked that idea, said he has seen it implemented somewhere. But it was scrapped, cos of the sheer volume. (i dont wonder what he is talking about).
Just as an afterthought i do wonder how long will Gmail function. (wont it be complicated using XmlHTTPRequest all over your page).
A web service (or maybe just a ASP page) renders and serves an XML generated based on the inputs passed to it.
A web browser picks it up, uses XSLT to transform it into a lovely page.
And what do you get, an application which does not waste too much time on the server.
Do not speak, just think.....Does nt your mind do a full revolution???
Anyway my friend really sparked that idea, said he has seen it implemented somewhere. But it was scrapped, cos of the sheer volume. (i dont wonder what he is talking about).
Just as an afterthought i do wonder how long will Gmail function. (wont it be complicated using XmlHTTPRequest all over your page).
Comments
The biggest problem would be that old browsers do not know how to handle XML.
One way of handling this problem would be to have a server-side browser sniffer.
if browser=old
XSLT from xml to html
else
send xml
But, on second thoughts, is it so much of a waste of time on the server to generate markup? What about the effort the server will have to put in to generate the XML in the first place?
The real benefit of this would be if there are many types of clients consuming the XML and processing them (in any way). But if you are really only making web services that are used to generate web-pages, XML is hardly that useful.
But then again, you could talk about future-proofing...