From: Jason Purdy <suppressed>
>This could work nicely in the cgiapp with one runmode to
>put together the template and another runmode to output
>the PNG file.
Why can't the "src=" attribute refer to a CGI and let the visitor's browser contact that URI when it receives the page content from your C::A application? To the browser it doesn't care. It's just a URI it is told to contact for the image content.
Why would the graph-producing application have to be a C::A app, or wedged into your existing C::A app as another runmode? Isn't this a good candidate for a standalone CGI? It's not producing HTML. Just image content. The only thing that might make it a little more complex than serving image content is if it's semi-realtime (images change every 15 minutes) and you want the image-producing CGI to detect whether it should emit the last image generated, or generate a new one and emit it.
Mark
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.