Re: [PEPr] +1 for System::Daemon
| From: | Kevin van Zonneveld | Date: | Sun, 11 May 2008 12:22:01 +0000 |
| Subject: | Re: [PEPr] +1 for System::Daemon | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-50082@lists.php.net to get a copy of this message | ||
Thanks.
I've added Michael & Till's suggestions to my todo list. Till, to
answer your question:
On Sun, May 11, 2008 at 12:51 PM, Till Klampaeckel <till@php.net> wrote:
> I also find the "usePEAR" stuff rather misleading, is this necessary since
> you are proposing to PEAR? I am not sure why all those conditionals are in
> the code. For example, you have code checking for exception classes, etc..
> I would just make sure it loads them properly ("require_once
> 'System/Os/Exception.php';") and be done with it.
In it's current form, System_Daemon still works if you don't have PEAR
available on a server.
The default is just to use PEAR, but it runs in standalone mode when
you specifically tell it to start($usePEAR = false);
This gives you the freedom to expiriment or include System_Daemon in
existing projects without having to install/upgrade PEAR and maybe
worry about affecting other projects/sites on a server.
Of course using stand-alone mode denies all of PEAR's advantages
(exceptions, updates, log package, etc), but currently that's entirely
up to the end-user/developer. There are some projects that have this
package as an SVN:external, and require nothing else to run except for
Linux & PHP-CLI > 5.2.1
If it is a deal breaker I can always remove all the conditional
PEAR-independent-code & make it PEAR-only, but I personally would like
to maintain this duality. Let me know.
--
Kind regards,
Kevin van Zonneveld
Work | http://www.true.nl/
About | http://kevin.vanzonneveld.net/