Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51943 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84960 invoked from network); 20 Apr 2011 12:25:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Apr 2011 12:25:23 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 unknown Solaris 10 (beta) Received: from [217.114.211.66] ([217.114.211.66:36329] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A6/A0-15607-8A0DEAD4 for ; Wed, 20 Apr 2011 08:25:13 -0400 Received: from [192.168.2.230] (ppp-93-104-36-58.dynamic.mnet-online.de [93.104.36.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 7CDB14BD8C; Wed, 20 Apr 2011 14:25:08 +0200 (CEST) Message-ID: <4DAED086.7050209@schlueters.de> Date: Wed, 20 Apr 2011 14:24:38 +0200 User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.9) Gecko/20101021 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Michael Morris CC: David Muir , internals@lists.php.net References: <4D704BA5.5080402@oracle.com> <14.AE.01409.86D7DAD4@pb1.pair.com> <4DAE44FA.6020305@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFC: built-in web server in CLI. From: johannes@schlueters.de (=?ISO-8859-1?Q?Johannes_Schl=FCter?=) On 04/20/11 02:05 PM, Michael Morris wrote: > This takes advantage of the fact that this CLI client, which will*not* be > running as a daemon, will have an open terminal window for it for as long as > it persists until the process is stopped with CTRL-C. Sending output to > that terminal window would be*very* useful in my opinion, hence the call > for trace. Essentially, trace is "echo" to that terminal window, or > "print_r" to that window if it is given an object or array. error_log() output should go there by default. (didn't check the patch) you can route everything there. I don't think it's good to add tons of extra functions for that. johannes