Re: [Php-java-bridge-users] SERPRO will join project: what skills are in need at the bridge project?

[<php...@li...>]

Hi Andre,

this sounds very interesting!

At the moment the code contains a lot of old cruft which nobody
understands, but which is kept for backward compatibility.

For example I would like to get rid of the following "features"

* java_require() and dynamic class loading

* The PhpCGIServlet and the CGIServlet. The FastCGI servlet should be
rewritten.

* .NET and mono support is obsolete

* the custom log4j support should go

* everything from the bridge/http/ package should be removed. These
context runners are difficult to understand. I would use chunked
connections everywhere.

* Remove the autoconf scripts and support for RedHat's GNU Java/GCJ.
Developers should be able to use a Java IDE like Netbeans or Eclipse to
contribute to the project.


What about creating a fork, something like "PHP/Java Bridge light"? The
old PHP/Java Bridge code could still be maintained by me. And bug fixes
could be taken from the new code base.

Do you need a new SVN or GIT repository or is a branch sufficient?


Regards,
Jost Bökemeier