Chris Savery wrote:
> Hello,
>
> I notice that the encoder doesn't work with PHP5. This is something I
> would really like and since I'm an experienced C/C++ programmer, 10+
> years work experience, I wonder if this is something I may help out with
> in getting it working. I'm not yet familiar with any eA internals so my
> initial question would be is this doable in some reasonable amount of
> effort or is it a really big undertaking? Do you seek out or want more
> developers to be involved in eA? I have some time available but not all
> my time...
>
> Chris :)
>
Hi Chris,
The encoder needs so much work that it would be best to rewrite it from
scratch. At the moment the encoder and cache part have a lot of
duplicate code, which both needs to be updated on every change in the
Zend Engine. The encoder would need to be rewritten so it can
serialize/deserialise the cache structures the caching code generates.
This way decoding should only be done once and could be cached afterwards.
I've been looking at PHP6 with ZE3 and it changes a lot because it will
support unicode strings. This means that the caching code will have to
be fully revised and also the encoder. So I'm a bit reluctant to start
working on a new encoder and risking having to throw it away again.
I checked out bcompiler on pecl yesterday and it fully support php5.1,
so maybe it time for eAccelerator to give up on the encoder because
there is an alternative with a more attractive license (PHP instead of
GPL). This would mean that a company can make some small changes to the
encoder/decoder and distribute a binary loader, this way it would be a
lot more difficult to decompile a script.
I'm a huge opensource fan and I don't like the idea of distributing
binary php scripts but I realize that it isn't that easy for a company
to distribute it's webapplications in source, so an encoder is needed. A
encoder in eAccelerator means that the source needs to be available at
all time. Writing a disassembler is pretty easy when you got the full
source.
On the other hand, all help is welcome. If you would like to work on it,
I would happy to get you going and accept patches.
gr,
Bart
--
Bart Vanbrabant <bar...@zo...>
PGP fingerprint: 093C BB84 17F6 3AA6 6D5E FC4F 84E1 FED1 E426 64D1
|