A colleague and I are contemplating an ultra-basic server-based cgi engine.
You can tell most webservers what *.exe to run for a particular file extension (jsp,asp,cfm,etc)
So If I wrote such an executable, what can I expect the webserver to send?
-The file's ascii data directly in a stream?
-a filename of the file requested?
-(ugh) a pointer to the file requested?
...Then, once I've parsed out the html and "interpreted" my tags, how do I send the "new" html back to the client "through" the webserver?
I think these 2 tasks are relatively simple, but I just don't know how cgi engines rcv/send via a webserver process.
Many, Many thanks for any insight you can offer.
-Jerry
You can tell most webservers what *.exe to run for a particular file extension (jsp,asp,cfm,etc)
So If I wrote such an executable, what can I expect the webserver to send?
-The file's ascii data directly in a stream?
-a filename of the file requested?
-(ugh) a pointer to the file requested?
...Then, once I've parsed out the html and "interpreted" my tags, how do I send the "new" html back to the client "through" the webserver?
I think these 2 tasks are relatively simple, but I just don't know how cgi engines rcv/send via a webserver process.
Many, Many thanks for any insight you can offer.
-Jerry