Re: [Templates] TT2, Apache2, mod_perl2, Apache::SessionManager

>> Me too, I haven't already played around with libapreq2 since it's

Mike Whitaker wrote:
>> Me too, I haven't already played around with libapreq2 since it's
>> still under
>> development but the problem seems to be the different API. I hope to
>> better
>> investigate this next week.
>> Currently I'm very busy, so now the workaround it's to remove/rename
>> libapreq2
>> Apache::Cookie (thanks to Geoff for the suggestion :-))
>>
> 
> The annoying thing (*grin* - just kidding) is that Geoff's
> Apache::Template patch seems to require libapreq2, so...

well, it's not my patch that requires it.  really, the only work I did was
to alter Apache::Template for mp1 to use the new directive handler API for
mp2, since they are completely different between the two versions.  that, a
bit of API tweaking, and the addition of some tests were about all I really
did.  Template::Service::Apache requires Apache::Request in both the
official release and my little hack.

> 
> I might need Apache::Cookie in other code in this server, so I'll see if
> I can patch Apache::SessionManager to not *use* Apache::Cookie via a
> PerlSetEnv.

yeah, that's what I was going to suggest - give the user the option of
choosing whether to use Apache::Cookie or CGI::Cookie.

oh, and enrico, you can reduce the amount of mp2 logic by not compiling
constants into the Apache class - if you don't use the -compile option with
Apache::Const then you get them in the current package, so OK (and not
Apache::OK) would be the call, allowing both mp1 and mp2 to look the same.
it adds another symbol table entry, but keeps the code cleaner so I guess
you can decide which is more important :)

HTH

--Geoff

_______________________________________________
templates mailing list
templates@xxxxxxxxxxxxxxxx.xxx
http://lists.template-toolkit.org/mailman/listinfo/templates