As I said here before and because you are so damn persistent I will
say it again. The main reason is maintenance. The shm functions are
not cleanly integrated in eAccelerator. So we had to make a choice:
either we make sure that the few people that are to stubborn to use
something else can use the shm functions, or we invest the little time
we have for eA in keeping it up to date with php. There is only a very
small number of people using those functions. To date only a handful
of people complained of the thousands of users. Only one person keeps
complaining!
I never said that you could use the shm_ functions in php directly. I
did say that you can use them to implement an api that is similar to
the eA shm functions. You can also implement this in C using almost
the same functions. Your choice. If somebody ever implements it, we
will consider hosting it next to eA script cache. Integrate those two,
never.
gr,
Bart
> --
> You received this message because you are subscribed to the Google Groups "eaccelerator" group.
> To post to this group, send email to eaccel...@googlegroups.com.
> To unsubscribe from this group, send email to eaccelerator...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/eaccelerator?hl=en.
>
>
--
Bart Vanbrabant <ba...@vanbrabant.eu>