--On June 15, 2007 5:28:36 PM +0200 Dagobert Michelsen dam@baltic-online.de wrote:
What is missing:
The new backend is not 100% compatible to the old backend due to the lack of data sharing. This is a complex issue but maybe solvable with the help of the mod_perl code. Alternatively the code could fall back to a single interpreter when compatibility mode is on. I am trying to avoid legacy compatibility code in the C part and move that to a Perl module interposed between back-perl and the oldstyle module. To make this as easy both for legacy- and new users is a thing I am still working on. Personally I dislike the idea of breaking compatibility, however I don't know how much people actually use the Perl backend broken as it is. The new API is designed to be as extendable as possible to avoid incompatible changes in the future.
I think very few people use the current back-perl. I would be fine if the new one dropped any attempt at compatibility going backwards if it was included in the 2.4 release. As you noted, as it exists now, it is pretty much unusable, and anyone wanting to use it in 2.4 should update. Just my 2c. ;)
--Quanah
-- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration