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.
It can, but that's still gathering the same data twice.
Why would the graph-producing application have to be a C::A app, or wedged into your existing C::A app as another runmode?
It doesn't -- just trying to keep it relevant here. ;) Actually, one benefit of having it within the same cgiapp is that you could rely on the code being in all one place and better reusage.
> ... 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.
That's interesting. The underlying data is changing a lot right now, but in the future, that'll slow down. So I could tuck a max(id) in the Storable file and do a quick query to see if that's less than the current max(id) of the db. If so, then do the re-gen.
Thanks, Mark! I'm also interested in more feedback and ideas.
- Jason
--------------------------------------------------------------------- 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]
