sysv ipc
| From: | Mattias Norlander | Date: | Thu, 06 Jul 2000 15:00:34 +0000 |
| Subject: | sysv ipc | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-23721@lists.php.net to get a copy of this message | ||
Hi!
First of all: 1Kthankyou for a great tool, I've used php for a
while now and I think it serves it purpouse wery well!
But ... ;)
When I first saw that php supported sysv ipc functions for
semaphores and shared memory I got really excited. This offered the
possiblity to build very powerful solutions with different programs
talking over shared memory.
But as I start to use the functions I realize that they really don't
do what I expect. It seems that they are written so that php scripts
can talk to eachother, using a key/value data structure for the data.
Making other applications (writte in C or Perl for example) talk to
php scripts is not an easy task.
So what I'd like to know is (I've tried to find some answers to this
in the mailing archives, with no success):
o What is the original purpouse of the sysv ipc functions (in php), is
it just to allow different php programs to communicate or is there some
(simple) way for programs in other languages to take part ?
o If not, what are the future plans for this issue?
I would like to see a set of more "direct" functions just wrapping the regular
semop, semget etc.
Another alternative is to write a c library that handles shared memory
in the same way that php does and then distribute this library with
the php distribution. One could then also quite easily write wrapper
modules for other languages such as perl and python.
Well, that's it really!
--
Mattias Norlander
mattias@umc.se