On 24/06/13 19:36, Jan Kaluza wrote: > I think the separate "xs24" directory is easier to implement definitely. > Maybe it doesn't have to be whole xs directory, but just xs/maps and > xs/tables subdirectries. Someone would have to check that :).
I think I don't like the idea of having separate directories because later on if you want to change something you always have to look out to change it in all the places. On the other hand, keeping one set of maps may also lead to very complex code with multiple instances of the same thing. So, I'm not quite sure which way to go. >> > Will this be backward compatible with 2.0.x? > Partly. It depends on the httpd API you rely on. Lot of things changed > [1] between 2.2 and 2.4 and that is reflected also in httpd24 branch code. > If you check the revision log for the modperl tests in the httpd24 branch, > you can get better idea about changes. > > I think it's not possible to keep backward compatibility with 2.0.x. Some > API changes (like the auth API or just simple remote_ip/remote_addr struct > fields) are just so different that we can't make them backward compatible. Completely true. The problem with such a compatibility layer is that it raises false hopes that your software works with the new code if you just change a tiny bit. Thanks, Jan, Niko, for all the work. Jan, why do you think you don't have permission to commit to trunk? I wouldn't say that is true. Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@perl.apache.org For additional commands, e-mail: dev-h...@perl.apache.org
