Porter wrote:
> Ideally the script engine would have a "request" object - one of the
properties of the request would be the named arguments that had been
supplied when the page was requested - thus the URL for this page might have
read:
>
> http://www.myserver.net/test.rsp?condition=true
Check out:
Title: "CGI Form Dumper"
Date: 19-July-1999
File: %cgidump.r
Purpose: {
Display the contents of a submitted form as a web page.
Useful for debugging CGI forms.
Available at http://www.rebol.org
> Or - the rsp page could be entirely a Rebol script, overriding any sort of
HTTP headers, and spitting back binary data - perhaps to generate an image
on the fly.
Check out:
Title: "GIF number generator"
Author: "Jan Strejcek"
File: %gif-number.r
Available at http://www.rebol.org
> Or - if the rebol script generates a page, perhaps the <HTML> <HEAD> tags
could be autogenerated such that they include meta tags, and the <TITLE>
block simply transcribes the Title: from the rebol header...
Check out my HTML dialect available at http://www.rebol.org or latest
version on my web_dialect list at onelist.com
> Of course, most of this seems to be well beyond the current capabilities
of Rebol (as it stands right now).
:-\
> I think it'll be possible to get a rebol based web server to execute .r
files, and spit back the output of those scripts - but w/o multi-threading,
it's performance under any load will be poor.
Use Apache module, out soon. Or use the beta.
Andrew Martin
Beyond the bleeding edge...
ICQ: 26227169
[EMAIL PROTECTED]
http://members.xoom.com/AndrewMartin/
-><-
