Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:88721 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63647 invoked from network); 9 Oct 2015 18:32:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Oct 2015 18:32:56 -0000 Authentication-Results: pb1.pair.com smtp.mail=larry@garfieldtech.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=larry@garfieldtech.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.29 cause and error) X-PHP-List-Original-Sender: larry@garfieldtech.com X-Host-Fingerprint: 66.111.4.29 out5-smtp.messagingengine.com Received: from [66.111.4.29] ([66.111.4.29:57462] helo=out5-smtp.messagingengine.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2C/01-57614-75808165 for ; Fri, 09 Oct 2015 14:32:56 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E8534202B9 for ; Thu, 8 Oct 2015 17:14:05 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 08 Oct 2015 17:14:05 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=z6/YRb8lpKC2u7+ B/izeD5HqACE=; b=SvpLxQv5EWVm2Q4DzG6S2e+RnnnPQqtowqDEHrppMhhsXqZ QdyXK6AOKhNnPm/pTv1DooecVpQB/g9MSAsSbNTYhuAWGWUMnqpvvqeaklMTRuEp Fw38BZk3R5QY6EkOw81xjflJbbvVBT38/Y0TSxj47qI9IdZAD+JvfCoOuAVE= X-Sasl-enc: XX4wLv9j4XEiQ8D5fXP36VExRnN0SqUzptXW0IcB6UNS 1444338845 Received: from [172.20.14.203] (rrcs-98-103-215-66.central.biz.rr.com [98.103.215.66]) by mail.messagingengine.com (Postfix) with ESMTPA id AAD88680114 for ; Thu, 8 Oct 2015 17:14:05 -0400 (EDT) To: internals@lists.php.net References: <56095A0C.4070306@cubiclesoft.com> <1443529244.15520.67.camel@kuechenschabe> <560AACB6.9080909@cubiclesoft.com> Message-ID: <5616DC9D.6040201@garfieldtech.com> Date: Thu, 8 Oct 2015 16:14:05 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] async/await - is future reserved words in PHP 7.x? From: larry@garfieldtech.com (Larry Garfield) On 10/01/2015 01:59 AM, Stephen Coakley wrote: > So then, in summary, threads & multiprocessing enables you to do more > *work* simultaneously, while async **maximizes the usefulness of each > thread you have**. So using both is actually an incredibly good thing, > but they aren't the same nor accomplish the same thing. I hope what I > said made sense. Well, you've successfully convinced me that PHP needs both multi-threading and async IO. I hope you're happy now... --Larry Garfield