Andy Wardley wrote: > I've been playing around with Apache 2 and mod_perl 1.99 and considering > the changes I'll need to make to Apache::Template to make it play nicely > under the new world order. > > Given that I want to continue to support Apache::Template for v1 users, > should I create another module, say Apache2::Template, or is there some > preferred approach to v1/v2 compatabilities that I should consider? > > I've read the compat.html doc and understand that I might be able to > support Apache::Template as it is with the help of the Apache2 compatability > module. However, I'm sure there are some parts, server/dir merging in > particular (which seem to be broken in v1 anyway), which are going to need > new implementations for v2, so I figure it's probably worth forking the > codebase sooner rather than later.
No Andy, no need to rename, you can either maintain the two in one module (if it's not too messy, which is the case if you have a lot of C) or just two different versions which will install themselves into different dirs. Here are some preliminary notes discussing these issues. http://perl.apache.org/release/docs/2.0/devel/porting_from_1.x/porting_from_1.x.html Feel free to help improving on these. Of course the MP_INST_APACHE2=1 mechanism needs to become available to to other module writers. __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
