Re: <inc> in ncsa server
robm@ncsa.uiuc.edu (Rob McCool)
X-Delivered: at request of secret on dxcern.cern.ch
Message-id: <9310070717.AA09002@void.ncsa.uiuc.edu>
From: robm@ncsa.uiuc.edu (Rob McCool)
Date: Thu, 7 Oct 1993 02:17:05 -0500
In-Reply-To: Charles Henrich <henrich@crh.cl.msu.edu>
"<inc> in ncsa server" (Oct 7, 12:43am)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: Charles Henrich <henrich@crh.cl.msu.edu>, www-talk@nxoc01.cern.ch
Subject: Re: <inc> in ncsa server
/*
* <inc> in ncsa server by Charles Henrich (henrich@crh.cl.msu.edu)
* written on Oct 7, 12:43am.
*
* I know of a couple sites who are using it to add the last modification date on
* the end of the file pages.
*
* I for one use it all over the place, its integral to all my weather
* stuff, as well as system status information, inlined filesizes of items and
* the like.
*
* Its mighty useful, it provides the same sort of extendability the plexus
* server gives, if not more. (And its in C :)
*/
Something Tony and I were recently discussing is the possibility of making a
"standard" preprocessor for HTML documents. This way, you would have regular
HTML documents (which would not be parsed, just sent by the server), and you
would have a new type like HTML-macroized. When the client requests a
document of this type, the server would run the pre-processor on the
HTML-macroized document, which would then spit out an HTML document to
return to the client.
This way, it would be "just another document conversion" to the server, and
if we agree on a standard preprocessing format, it will work on all servers
that support it. It also does not add tags to HTML which really don't belong
in HTML itself.
What do you think?
--Rob