Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67550 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16083 invoked from network); 27 May 2013 08:15:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 May 2013 08:15:42 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:58542] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 97/30-32733-D2613A15 for ; Mon, 27 May 2013 04:15:41 -0400 Received: (qmail 12077 invoked by uid 89); 27 May 2013 08:15:38 -0000 Received: from unknown (HELO com.flipdogsolutions) (lester@lsces.co.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 27 May 2013 08:15:38 -0000 Date: Mon, 27 May 2013 09:15:36 +0100 To: =?UTF-8?Q?Leszek_Krupi=C5=84ski?= ,Sanford Whiteman Message-ID: <6c6c2a5a-8762-48fc-9a71-0e9c5dca82a5.maildroid@localhost> In-Reply-To: <293168642.20130527032001@cypressintegrated.com> References: <51A092FC.4010700@wikimedia.org> <51A1AF3E.5000704@sugarcrm.com> <51A2D395.5030302@sugarcrm.com> <1022965181.20130527011024@cypressintegrated.com> <51A2FD10.7030906@gmail.com> <293168642.20130527032001@cypressintegrated.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_0_1137789408.1369642536310" Subject: Re: [PHP-DEV] date.timezone E_WARNING -- Really necessary? What's the rationale? From: lester@lsces.co.uk ------=_Part_0_1137789408.1369642536310 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit > In my opinion UTC is a good compromise. I agree that _in the absence of any other setting_ there's nothing wrong with using UTC! Let be clear: UTC is a perfectly fine hands-off default rather than issuing a warning. Non-technical end users will guess you're on London time but whatever. And if you think 'London time' is UTC then you will get just as many problems half of tbe year. Once one is WORKING using timezones, you need to actually understand that for some timezones, the time will be an hour different for half of the year and simply assuming that the time offset from the browser is correct is as bad as assuming UTC is London time. The many problems being tributed to automatically setting a server timezone were always more due to understanding that the server was getting things like daylight saving wrong. Set the server to UTC and then select a DISPLAY timezone makes managing time a lot easier. Add to that the option to user a client set timezone and one is good to go .... -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php ------=_Part_0_1137789408.1369642536310--