I use a method combining both; I first write a so-called
'print.php' which has the ability to write a outputted page to a
disk cache on the disk. So pages are only generated the first
time they're accessed;  on second and further requests they're
serverd directly from the cache (disk in my case).


they're accessed 
On Wed, Jun 27, 2001 at 06:13:25PM -0400, [EMAIL PROTECTED] wrote : 
> Question for all you php experts out there: 
> My organization's website is based on mysql/php backend - 95% of the
> webpages are generated dynamically using templates and database records. 
> We have been asked to create "printer-friendly" versions of these pages. 
> Now for your opinion/advice: should we (1)create another template called
> "print.php" for example and generate there print friendly pages dynamically
> or should we (2)create static html copies of each database record so that
> they are "print friendly"? 
> By "print friendly" I mean I want a page that doesn't have the text cut off
> the right hand side of the page (nevermind, for now, that the original page
> shouldn't do this 
> in the first place :) ) 
> Thank you so much for your help! 
> - Shawna 

Markus Fischer,  http://guru.josefine.at/~mfischer/
EMail:         [EMAIL PROTECTED]
PGP Public  Key: http://guru.josefine.at/~mfischer/C2272BD0.asc
PGP Fingerprint: D3B0 DD4F E12B F911 3CE1  C2B5 D674 B445 C227 2BD0

PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to