-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 * Christopher L. Everett <ceverett at ceverett.com> [2003-07-22 08:54]: > I'm a Template-Toolkit newbie/possible convert.
"I want to believe!" :) > I'm researching the best way to integrate TT and Class::DBI because > I'm attracted to the concept of filling templates by pulling data from > objects. This just came up on cdbi-talk (the Class::DBI list) last week; see <http://groups.kasei.com/mail/arc/cdbi-talk/2003-07/msg00156.html>. > Second, (and correct me if I'm wrong on this), configuration is global > across entire servers. That is correct, mostly due to how TT handles configuration (see below). > But then it appears that since I'm moving the configuration directives > into a different file I could ditch Apache::Template and TSA entirely > and just grab the configuration (out of cache if possible), like this: Yep, Apache::Template is just a front end to the Template::Service::Apache object. If you were to write your own front end, start with Template::Service, and not Template -- Template simply decides where to send the output of Template::Service, and you already know where you want it to go (to $r->print). > Any thoughts before I go off the deep end? It's difficult to do what you want to do, because for the most part, the attributes of Template::* objects can't be changed (unless you're willing to get naughty and start poking at data members). The other alternative, a separate set of Template objects per virtual host, gets memory intensive quickly. (darren) - -- A lot of people mistake a short memory for a clear conscience. -- Doug Larson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: This message is digitally signed and can be verified for authenticity. iD8DBQE/HTemzsinjrVhZaoRAnl5AJ48zakSOPBBBqWEEW4uWqRgaH017ACgkLtk 6PF6dLK7WzgO7CHWQR5JBRM= =i3DX -----END PGP SIGNATURE----- _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
