On Mon, Sep 21, 2009 at 3:20 PM, Raphael Geissert <geiss...@debian.org> wrote: > tag 547534 wontfix > It is called a SAPI for a reason, were they fully compatible they wouldn't be > two different SAPIs.
You are wrong here. The php team generally do not want to replace the old fcgi sapi. It would cause too many issues not to keep the old one available. Even if the a SAPI were also fgci - compliant, it would still be a different sapi. Its been discussed already. > None of which is of our interest as the code and the server are in Debian > main. I don't fully understand that sentence, but i believe these things shouldn't be dismissed out-of-hand. Generally all users want to be able to serve php faster, with a lower memory overhead and optimize server performance. It costs money to run servers after all. This is something that impacts not just for the big companies, but for everyone who runs a php server. Why deprive many users of this and without a reasonable cause? Clearly these options aren't here yet. But they will be coming along so its clearly something to think about and plan ahead for. I'm sorry, however currently with these type of closed response it becomes impossible to include Debian to make a good plan for anything worthwhile here. Best regards, dreamcat4 dreamc...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
