Skip to main content

Just Thinking....

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

Comments

Rakesh Pai said…
This is not a new idea, and I've seen this being done at a lot of places myself. But this idea is not without it's set of problems.

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

Popular posts from this blog

My first problem with AJAX

I was using Callback (AJAX) to retrieve a page i had developed . Lets start all over, I was using AJAX to retrieve a part of the contents of a web page. Cool, simple, it downloaded without a pain, then I innerHTMLed it to a span tag. Worked fine, successful, clapped my hands etc.etc. Clicked on the button which had seemed to appear out of nowhere. And then, it all fell apart. The feared exclamatory symbol appeared on the status bar.... And for the newbies, thats an indication of a JavaScript error in IE. Of course, as usual i was all curses at my IE window......Anyway to make a long story short (i AM quite sleepy u know). the scripts which i seemed to be innerHTMLing to the span tag are not executed. And what i mean is anything between the script tags which have been innerHTMLed to that span tag are not executed. Of course i can see a ray of hope in the distance. I mean the distance till tomorrow morning. And just for kicks, check out a hi-fundoo flash file titled EPIC 2004 . And for...

Imagine...an internet based world

Was reading "The Google Story", when i got this wierd idea. Consider a stripped down version of Linux, meant only for doing simple things such as browsing the internet, to read from the various drives (which is primarily meant only for storage of personal data), to play music and some single-player games. All the rest provided by the internet. Information searching/Chatting/Mailing/Documentation editing/journal maintenance/daily schedule maintenance/news/rss/shopping, etc. What else will you use for your computer for? Ok, actually i have been working on mainframes for some time now and am getting adjusted to the "dumb terminal" concept. Then i started associating the concept with scenario we are observing all over the net. As a matter of fact this will reduce the power of processing required on the client side also!!! Looks like the world is changing.... for the bettter, yup, i am sure. technorati tags: New internet age , dumb terminal , internet based world

Changing JAVA_HOME on a HDP 1.1 Hadoop on Windows Setup

We were setting up a small cluster of  Hadoop for some requirements, and decided to go with the HortonWorks release of Hadoop. ( HDP 1.1 for Windows ). After installing, we realized that for some reason the Oozie service was not starting up . (we tried both the CLI command provided with the HDP installation, as well as trying to manually start the service via services.msc). Looking through the log files (<HDP 1.1 installation path>\oozie-<version>\Service directory, specifically the oozieservice.out.log file) we found the error -    and so realized that Oozie server is dependent on JDK. It does not work with only JRE. To correct this we uninstalled JRE, and installed JDK. We also manually modified the JAVA_HOME environment variable to point to the new installation path. And then Oozie server started working all fine. But all the rest of the services (hadoop jobtracker, hadoop datanode etc.) stopped starting. Checking the logs of the services, we fou...