Regarding System_Socket

["Carl Fürstenberg"]

When I've looked at the socket interface in php I've felt it been a
bit low level and where looking for an more OO alternative; I found
System_Socket in your PEAR repository, but it hasn't been updated in a
while and marked as unmaintained. I would love to take over this
package, and possibly rewrite it from scratch.

I haven't been involved in PEAR development before; I've not used the
current System_Socket package in production, but my work as software
developer for the Bubba Server has made me written an own OO interface
(although limited at the moment) to in a clean way handle connections
over unix sockets.

I hope there is nothing preventing me to take over this package and
rewrite it from scratch, but if there is I would like to be able to
create an new package instead.

/Carl Fürstenberg

--
/Carl Fürstenberg <azatoth@...>

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[Kevin van Zonneveld-3]

While I'm not the right person to say anything about the takeover, I
do have some thoughts about System_Socket in relation to my package
System_Daemon. I'm curious to hear yours.

There may be some common ground between the packages.
I regularly get requests for socket code in System_Daemon. Seems a lot
of people want to interact with their daemons using TCP connections.
Mostly to just exchange instructions & feedback, but sometimes socket
code is the base of the actual application. Think someone building a
chat server running in a server's background.

However you can also control a daemon with very basic POSIX signals
(start, stop, reload, that kind of thing) and that's why there also
are a lot of uses for a daemon that don't require open sockets (think
a logrotate, sms queue daemon, etc)
Hence I felt socket code shouldn't be a part of System_Daemon itself,
but probably of another PEAR building block.

Now that it looks like System_Socket is maybe getting a revamp - what
do you think about teaming up for a smooth integration? I don't mean
merging the packages or anything (let's keep each package good at 1
thing), but we could:
- add an optional dependency from deamon -> socket, or maybe the other
way around?
- make sure they play together nicely
- supply simple examples e.g. how to build a daemonized chat server,
or maybe a key/value store.

--
Met vriendelijke groet / Kind regards,

Kevin van Zonneveld
http://kevin.vanzonneveld.net

http://twitter.com/kvz

2009/10/25 Carl Fürstenberg <azatoth@...>:

> When I've looked at the socket interface in php I've felt it been a
> bit low level and where looking for an more OO alternative; I found
> System_Socket in your PEAR repository, but it hasn't been updated in a
> while and marked as unmaintained. I would love to take over this
> package, and possibly rewrite it from scratch.
>
> I haven't been involved in PEAR development before; I've not used the
> current System_Socket package in production, but my work as software
> developer for the Bubba Server has made me written an own OO interface
> (although limited at the moment) to in a clean way handle connections
> over unix sockets.
>
> I hope there is nothing preventing me to take over this package and
> rewrite it from scratch, but if there is I would like to be able to
> create an new package instead.
>
> /Carl Fürstenberg
>
> --
> /Carl Fürstenberg <azatoth@...>
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php