Hi everyone,
I'm a php-java-bridge user, in windows environment and the performance
penalty is very relevant for our needs and so, i've alocated some time
(without priority mind) to build the module into a windows dll.
I'm trying (time allow) to "understand" the windows build requirements
(not an easy task with all the obscure "Zend" stuff around) for it and
build an Ant/Nant file to build it easier.
I've had some success in some of the building steps, but it is still a
work very much in the process.
I know it won't be much, but this is the help i can provide...
Cheers,
Luis Ferro
php...@li... escreveu:
> Hello, Jost
> It is fundamental to attract and retain more developers to use the repository for development.
> Now is time to call for more help on rpm packaging and having a healthy repository is a crucial step.
> I can compile and test on Debian, but another people could help on rpm compiling packaging.
>
> I was talking with other coleague and he still think that 2x performance penalty is a relevant issue. But one fully working implementation is better than many barely working and lagging behind the needs of developers.
> How many users has the pure C implementation?
>
> IMHO, if project offer different implementations, they need to be in sync.
> Or drop support for some while other people do not step in and help on compiling and packaging.
> The workload is seeming to be increasing too much over you.
> The project "bus factor" needs to be improved.
> Php-java-bridge is not an "end joe user" application. All users are developers. A skilled RH user may get the rpm compiling and packaging work from now.
> But the repository must be in sync with the development, as a development tool, not only as a "documentation tool" for this take off.
> As a suggestion, maybe another php-java-bridge-devel could be created.
> Any more suggestions?
> What can I do to help more?
>
> Regards.
> Andre Felipe Machado
>
>
>
> On Sat, 24 Mar 2007 15:56:41 +0100 (CET), Jost Bökemeier wrote:
>
>> Hi Andre,
>>
>> what about splitting the pure PHP implementation from the C based
>> implementation?
>>
>> Versions >= 4.0.3 may not compile anymore because I don't have the time
>> to check the compile scripts on a variety of operating systems and C
>> compilers.
>>
>> The pure PHP implementation allows us to experiment with certain ideas
>> or features very quickly, without having to worry about different
>> architectures.
>>
>> Is it necessary to keep the C based implementation in sync? The RPM
>> files for Red Hat are still at 4.0.1 and I don't want to update them until
>> a new version of Fedora is available.
>>
>>
>> Regards,
>> Jost Boekemeier
>>
>>
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> php-java-bridge-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users
>
|
