It sounds good to me as well. In our particular case I believe we still need to modify the ITK shell though. We have three different types of requests that may come in.
1. Normal A4D dynamic or static content request. 2. Request for very large file already sitting on a file server in the LAN. 3. Request for a file that needs to be created and may be of just about any size.
[snip]
$requestType:=A4D_RequestTypeIsACGI ($streamRef)
What does A4D_RequestTypeIsACGI do?
Aparajita,
I see Richard posted the code. I'll offer an explanation.
This looks like a modification of a technique I suggested to Richard that allows one to preprocess the request and determine if Active 4D should handle it. Using this technique is allowing me to transition a customer's web system from Netlink to Active4D/ITK. I can deploy existing web systems using the ITK web server (w/ minamal changes to tens of thousands of lines of existing Netlink code) while at the same time doing new development in Active4D. Many, if not all of the Netlink systems will eventually be rewritten using Active4D.
The general idea is that you look at the incoming stream, examine the header, make a determination based on some criteria (Richard's differs from mine), stuff the header back into the stream then return a result which determines whether Active4D or ITK handles the request.
I don't know whether or not you want to add this to the shell though as I doubt very few people besides Richard and myself are employing this technique.
--
Brad Perkins (mailto: [EMAIL PROTECTED]) DOE ARM Program/TWP Office - Los Alamos National Laboratory
