in reply to Images built on the fly do not display
You could try to make sure the image name is always different. Use a counter to increment a number, and use that as part of an image name. To delete old files, you could use a cron job; or you can have the parent do that, while it's waiting for the child to finish. You'll never have too many old files, that way. I hope. :-)
But my preference would be to invoke the image creating script directly from a separate CGI script (or equivalent), and send the image data directly to the browser instead of saving it to a file first. You do need to provide the appropriate content-type header, as others already have suggested, and then simply print out the image data. The parameters you now use on the command line, can be passed as part of the image URL, after a question mark, using the familiar GET URL syntax.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Images built on the fly do not display
by Anonymous Monk on Jan 08, 2003 at 11:41 UTC | |
by dws (Chancellor) on Jan 08, 2003 at 11:53 UTC | |
by bart (Canon) on Jan 08, 2003 at 12:02 UTC | |
by nosbod (Scribe) on Jan 08, 2003 at 13:50 UTC | |
by nosbod (Scribe) on Jan 08, 2003 at 12:57 UTC |