Re: Socket_Socket as "extended copy" of Net_Socket

As I said the possibility to create a listen sockets with it. (>servers) If somebody doesn't have "sockets" extension the new package can't work. So if sockets extension is not available a Net_Socket is being returned so the user can use it. Jon Parise wrote:

On Thu, Feb 06, 2003 at 07:41:38PM +0100, Stephan Seidt wrote:

I just suggested the "Socket" category some time ago and also its first package Socket_Socket. To use it seriously I thought about some compatiblity options with the Net_Socket package. What about sth like: if (!extension_loaded('sockets')) { return &new Net_Socket; } I copy Net_Socket to Socket_Socket and change the code in it to work with the new sockets. I also add the new functions bind, listen, accept, select, etc.

Why don't you just make Net_Socket "smarter"? Introducing two socket packages seems redundants to me (although I don't really know what additional functionality is to be provided by your Socket_Socket class).

-- if (!$TCPA->connect()) { throw new Exception('Sorry, no coffe today', EX_FATAL); }