Re: [PEPr] Proposal for System::Daemon

OK. But what do you mean by 'requires to open a port'? I mean, how are you going to communicate with a daemon? I am not really an expert in this area, but I assume there must be a way to send and receive the data from the daemon, and it's either via tcp port or unix socket. Kevin van Zonneveld wrote:

I could be wrong but I believe Net_Server - requires you to open an port, not all daemons want to do that - and includes a lot of 'socket-oriented' code - gives you limited control over the 'daemonization' (sighandlers, etc) - provides limited OS integration (logging, generating startup files) These are all points that System_Daemon will focus on. There isn't a lot of shared code or logic between the two packages and this is mostly because the focus of System_Daemon lays on the daemon itself, and not specifically building network servers. It basically should allow you to build any kind of application on top of it's foundation. -- Kevin van Zonneveld Work | http://www.true.nl/ About | http://kevin.vanzonneveld.net/

-- Open Source ALL content management with streaming video http://wiki.sharedlog.com