Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:33481 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52726 invoked by uid 1010); 28 Nov 2007 06:38:43 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 52711 invoked from network); 28 Nov 2007 06:38:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Nov 2007 06:38:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=indeyets@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=indeyets@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: indeyets@gmail.com X-Host-Fingerprint: 66.249.92.170 ug-out-1314.google.com Received: from [66.249.92.170] ([66.249.92.170:44850] helo=ug-out-1314.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1A/F5-02650-1FC0D474 for ; Wed, 28 Nov 2007 01:38:42 -0500 Received: by ug-out-1314.google.com with SMTP id m3so399072ugc for ; Tue, 27 Nov 2007 22:38:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Tjh0DzspWts10BqLvEnzCNgDbiZqGeYFLiJ1+pS49m4=; b=AIcXvVIsITX5aJ/Fb4qhhe4htijSAxr5DSCxPb5c14YsyB3bfWzwOq/ol8W6/rHdwAK7iodc8rc7PHWtqdovfFWiK3YtNVmb5LOBo07khTIPKLyM6peKJIf40yUYr5j9lcIP5tZS3LmPXNPX7xrmVOThF+nX1P2TnTZf89noimQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PbRQgILXFiVUYntXwTaeszwtjNUGAqk2mTw/H00S9HyvP2ftqZRspW8ge5ooF5k0GrGohSVEtxZKaMPbxZ5U8PV/FR8ZxV7/134eVzRWmAzRHnJpxaRBI9Kk/wXXwmJC3Wsf4Rz6QMb5KJ83XBp9I8WEMCWor9UgtqaEBpwL8+8= Received: by 10.150.229.16 with SMTP id b16mr1105156ybh.1196231917095; Tue, 27 Nov 2007 22:38:37 -0800 (PST) Received: by 10.150.57.12 with HTTP; Tue, 27 Nov 2007 22:38:37 -0800 (PST) Message-ID: Date: Wed, 28 Nov 2007 09:38:37 +0300 To: enugroho@spikesource.com Cc: "Rasmus Lerdorf" , "PHP Developers Mailing List" In-Reply-To: <1196206722.31863.16.camel@ganges.spikesource.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1196124442.21880.15.camel@ganges.spikesource.com> <474BA22F.2020608@lerdorf.com> <1196206722.31863.16.camel@ganges.spikesource.com> Subject: Re: [PHP-DEV] Reliable header sending mechanism in php 6 From: indeyets@gmail.com ("Alexey Zakhlestin") On 11/28/07, Ezra Nugroho wrote: > In my mind, it is still unreliable... > When I write my library, how can I enforce people who adopt it to enable > ob? > > Furthermore, I think it's quite annoying that some functions may not > work just because of an inclusion of a blank space somewhere in a file > that you don't maintain. > > As php applications get bigger, and developers have only a small scope > of the big picture, the reliability of the functions becomes bigger and > bigger deal. Enforcing people to use some specific way of coding to use library is incorrect, anyway. But, you can correctly handle the situation (i.e. provide a meaningful error to the user) by making a simple check: http://docs.php.net/headers-sent -- Alexey Zakhlestin http://blog.milkfarmsoft.com/