On Tue, Mar 23, 2010 at 2:04 AM, Per Jessen <per@xxxxxxxxxxxx> wrote: > > Use the right tool for the right job - PHP is a scripting/interpreted > language, it does not need threading (IMO of course). > > > -- > Per Jessen, Zürich (9.4°C) > > I couldn't agree more. But here's a real life example. Your client has a forum and is using phpbb for their in house use. They also have an in house custom PHP app, integrated with phpbb, built to suit their needs. Now they want to implement some kind of CMS. You come in and implemented a PHP based CMS to integrate into their existing applications. Then you realize something troublesome, you have a performance issue where it could be resolved by implementing thread. What are you going to do? Are you going to say to the client "We seem to have a problem. I suggest we migrate to Java or ASP.Net because threading will resolve the performance issue." Or are you going to spend who knows how long to try find a hack to resolve the issue? What do you think the client's response is when their need for the solution requires a short time frame of, if not immediate, implementation? Regards, Tommy -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
