MySQL db connections, queries (including multi-table joins), and
HTML::Template are so fast that you may be creating a solution for a problem
that doesn't exist.
Even if you write information (product info) into a session file, you will
still have to read it from the session file/db and roll it into
HTML::Template. So why add more code and set up the possibility for a loss
of data integrity (somebody updates the product info during a user's session
from "safe for kids" to "deadly poison"? (OK, that's extreme).
If it ain't broke, don't fix it.
-----Original Message-----
From: Mike [mailto:mikeharrison1@xxxxxxxxxxxxxxx]
Sent: Wednesday, July 21, 2004 6:45 AM
To:
Subject: [cgiapp] Caching HTML::Template output under CGI::App
Hello,
I have a database application which is very similar in structure to the one
given in the C::A example:
run mode 1: search form
run mode 2: access (MySQL) database and display results
run mode 3: detailed information on one item
Each run mode outputs to the browser using HTML::Template. The application
works fine, although I am concerned that when I return to run mode 2 from
run mode 3, it has to search through the database again before displaying
the same results.
Is there a way to get from rm 3 (via a link) back to the _template output_
of rm 2 without having to go through the whole rm 2 script (which opens a DB
connection, performs a select statement etc. then plugs the relevant
template variables into the template file, and finally outputs the template
to the browser)? I know it can be done with javascript:history.back(), but
what can be done for non-js browsers or browsers with js turned off? Am I
missing something that should be staring me in the face?
Any help/suggestions would be greatly appreciated.
Mike.
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
|
