Adam Gent wrote:

Hi,

There is no reason why it can not be all done within the C::A.

If the run mode generates the file and saves it to disk as a temporary file.
The run mode can then output the correct header.


What would the "correct header" there be?

Do you mean redirect the client to the temporary file that has been generated?

The other thing that I wanted to do was clean up the temporary file that was created after it has been sent to the user. This is achievable if C::A's run() method outputted the file itself (the cleanup code could then go in teardown()), but not if it just sent a redirect header.

- Steve


--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to