Mukul Gandhi wrote:
I was talking from purely theoretical perspective. i.e. a plain HTTP
Web Server that offers only HTTP support.
That's interesting. Because a POST request is part of the HTTP protocol
and declares an action to be taken that changes something on the server.
A GET request is also part of HTTP and declares a resource to be
retrieved without changing something on the server.
Even with the very earliest web daemons there was a CGI implementation
so that you could handle POST request. As there is nothing even remotely
standardized that says how to deal with parameters in a POST request.
Later (or at the same time), GET (and HEAD and TRACE and PUT and all
other messages) could be handled by a CGI handler.
And since you have all the freedom of a programmer, you can do anything
you like in your CGI script (C, C++, VB, Perl, Eiffel), amongst which
serving HTML pages which are a result of processing it by an XSLT engine
(which you can call in the manner you seem fit for your language).
Meaning: long before XSLT saw the light, you were able to serve data
passed through an (not yet existing) XSLT engine.
-- Abel
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--