Re: [PHP] Suggestions for the next php
Hello, Stephano Mariani wrote: > > I believe fork is very expensive in terms of performance. > One should consider that in the case of server modules (ISAPI in > particular) a huge overhead is incurred when forking. I better > alternative would be the vfork call. Or better still, the __clone call. I don't know exactly what pcntl uses. From the programmer point of view, the principle is the same as fork. > Do you know of any ways to implement this without changes to the php > codebase itself? I doubt it is possible for an just extension to do > this, it need the php core to support this. Ask Jason Greene. Regards, Manuel Lemos -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP] Suggestions for the next php
Hello, Rouvas Stathis wrote: > > Manuel Lemos wrote: > > > > > > For example, multi-threading. Looking at the PHP sources, I can see this > > > > would be fairly easy to implement on some most server modules. Before I > > > > get fried by people for suggesting this, I know there are many functions > > > > that are not thread safe, such the ob_* functions. But as far as I can > > > > see threading would be well suited to some PHP tasks... > > > > You can use the pcntl extension if you are using any (fork capable) > > Unix. > > Can you elaborate on the "pcntl extension", please? > What is it? It is an extension that lets you create child processes with Unix fork. It does not work on Windows because it can't fork. > How do you use it? You have to ask Jason Greene because it is not yet documented. Regards, Manuel Lemos -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP] Suggestions for the next php
Hello, Vincent Stoessel wrote: > > I did not know that, thank you for the info. > I just downloaded phpIDE beta and I am highly impressed with the > debugger. It say that it can do remote debugging as well. That sounds cool > but I wonder how secure it is. Zend folks, I apologize for taking so long to try out >this > product, it's great! There are plenty of IDE that can be used to debug PHP code. Zend IDE is just one of them. Actually, last time I tried it I didn't like it much because it is a Java application which looks like an alien program with a different look and feel from the platform you are using. That is because they use Swing rather than AWT. Regards, Manuel Lemos -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP] Suggestions for the next php
I believe fork is very expensive in terms of performance. One should consider that in the case of server modules (ISAPI in particular) a huge overhead is incurred when forking. I better alternative would be the vfork call. Or better still, the __clone call. Do you know of any ways to implement this without changes to the php codebase itself? I doubt it is possible for an just extension to do this, it need the php core to support this. Stephano Mariani -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Rouvas Stathis Sent: Friday, 21 December 2001 1:21 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [PHP] Suggestions for the next php Manuel Lemos wrote: > > > > For example, multi-threading. Looking at the PHP sources, I can > > > see this would be fairly easy to implement on some most server > > > modules. Before I get fried by people for suggesting this, I know > > > there are many functions that are not thread safe, such the ob_* > > > functions. But as far as I can see threading would be well suited > > > to some PHP tasks... > > You can use the pcntl extension if you are using any (fork capable) > Unix. Can you elaborate on the "pcntl extension", please? What is it? How do you use it? Thank you, -Stathis. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP] Suggestions for the next php
Manuel Lemos wrote: > > > > For example, multi-threading. Looking at the PHP sources, I can see this > > > would be fairly easy to implement on some most server modules. Before I > > > get fried by people for suggesting this, I know there are many functions > > > that are not thread safe, such the ob_* functions. But as far as I can > > > see threading would be well suited to some PHP tasks... > > You can use the pcntl extension if you are using any (fork capable) > Unix. Can you elaborate on the "pcntl extension", please? What is it? How do you use it? Thank you, -Stathis. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP] Suggestions for the next php
I did not know that, thank you for the info. I just downloaded phpIDE beta and I am highly impressed with the debugger. It say that it can do remote debugging as well. That sounds cool but I wonder how secure it is. Zend folks, I apologize for taking so long to try out this product, it's great! Manuel Lemos wrote: > Hello, > > Vincent Stoessel wrote: > >>I would love to see a decent debugger like perl has. >>Nothing is more frustrating then having to echo and die() >>to debug code. Especially when you are assigned the task of >>updating code from a developer that has long gone without >>leaving any documentation. >> > > PHP has a built-in debugger support. You can single-step, put > break-points, watch variables, etc... from many several existing > debugger GUI . > > > >>>I have been a PHP user since version 3.0 came out, and have seen it >>>develop a lot along the way, but theres some things I find it lacks that >>>it really should not. If people agree, I'll glady contribute to the PHP >>>codebase. >>> >>>For example, multi-threading. Looking at the PHP sources, I can see this >>>would be fairly easy to implement on some most server modules. Before I >>>get fried by people for suggesting this, I know there are many functions >>>that are not thread safe, such the ob_* functions. But as far as I can >>>see threading would be well suited to some PHP tasks... >>> > > You can use the pcntl extension if you are using any (fork capable) > Unix. > > Regards, > Manuel Lemos > > -- Vincent Stoessel [EMAIL PROTECTED] Java Linux Apache Mysql Php (JLAMP) Engineer (301) 362-1750 Mobile (410) 419-8588 AIM, MSN: xaymaca2020 , Yahoo Messenger: vks_jamaica -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP] Suggestions for the next php
Hello, Vincent Stoessel wrote: > > I would love to see a decent debugger like perl has. > Nothing is more frustrating then having to echo and die() > to debug code. Especially when you are assigned the task of > updating code from a developer that has long gone without > leaving any documentation. PHP has a built-in debugger support. You can single-step, put break-points, watch variables, etc... from many several existing debugger GUI . > > I have been a PHP user since version 3.0 came out, and have seen it > > develop a lot along the way, but theres some things I find it lacks that > > it really should not. If people agree, I'll glady contribute to the PHP > > codebase. > > > > For example, multi-threading. Looking at the PHP sources, I can see this > > would be fairly easy to implement on some most server modules. Before I > > get fried by people for suggesting this, I know there are many functions > > that are not thread safe, such the ob_* functions. But as far as I can > > see threading would be well suited to some PHP tasks... You can use the pcntl extension if you are using any (fork capable) Unix. Regards, Manuel Lemos -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP] Suggestions for the next php
I would love to see a decent debugger like perl has. Nothing is more frustrating then having to echo and die() to debug code. Especially when you are assigned the task of updating code from a developer that has long gone without leaving any documentation. Stephano Mariani wrote: > Hi! > > I have been a PHP user since version 3.0 came out, and have seen it > develop a lot along the way, but theres some things I find it lacks that > it really should not. If people agree, I'll glady contribute to the PHP > codebase. > > For example, multi-threading. Looking at the PHP sources, I can see this > would be fairly easy to implement on some most server modules. Before I > get fried by people for suggesting this, I know there are many functions > that are not thread safe, such the ob_* functions. But as far as I can > see threading would be well suited to some PHP tasks... > > I'd like to hear users thoughts on this. > > TIA, > > Stephano Mariani > > > > -- Vincent Stoessel [EMAIL PROTECTED] Java Linux Apache Mysql Php (JLAMP) Engineer (301) 362-1750 Mobile (410) 419-8588 AIM, MSN: xaymaca2020 , Yahoo Messenger: vks_jamaica -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP] Suggestions for the next php
Hi! I have been a PHP user since version 3.0 came out, and have seen it develop a lot along the way, but theres some things I find it lacks that it really should not. If people agree, I'll glady contribute to the PHP codebase. For example, multi-threading. Looking at the PHP sources, I can see this would be fairly easy to implement on some most server modules. Before I get fried by people for suggesting this, I know there are many functions that are not thread safe, such the ob_* functions. But as far as I can see threading would be well suited to some PHP tasks... I'd like to hear users thoughts on this. TIA, Stephano Mariani -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
