I'm a little confused as to how this is being used in common practice.
As it seems to me, the most practical way of using this -- and the
way that is displayed in most examples -- would be an inline request.
By that I mean you'd be including the file within the html itself,
<p>lots of baseball stats <img src='baseball.php'> </p>
<p>lots of baseball stats <?php require_once('baseball.php');?> </p>
But because of the way Output( ) generates the image, the header
information is always sent unless you write to file. If I were to
implement a plugin for any type of CMS out there, where the stats
would be generated on the fly, most likely it would fail because it'd
be re-sending header information.
Consequently, if this is unavoidable (I'm not really clear on dynamic
gd image creation & how header must be dealt with in order to get the
image to display properly) it would make sense that a caching feature
would be available.
If I'm blatantly missing something, please let me know. It's just
that I haven't been able to duplicate any of the examples I see
(images inline with content) unless the image is at some point
pre-generated and only after that point, added to the content.
Does that make sense to y'all?
Get latest updates about Open Source Projects, Conferences and News.