Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81225 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54719 invoked from network); 27 Jan 2015 10:54:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jan 2015 10:54:40 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:48448] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BB/67-18778-E6E67C45 for ; Tue, 27 Jan 2015 05:54:39 -0500 Received: (qmail 6441 invoked by uid 89); 27 Jan 2015 10:54:35 -0000 Received: by simscan 1.3.1 ppid: 6435, pid: 6438, t: 0.0710s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.189.147.37) by mail4.serversure.net with ESMTPA; 27 Jan 2015 10:54:35 -0000 Message-ID: <54C76E6A.4040903@lsces.co.uk> Date: Tue, 27 Jan 2015 10:54:34 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: internals@lists.php.net References: <54C732F3.8050304@beccati.com> <54C73A13.5030707@php.net> <54C75D2D.1010701@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Remove the date.timezone warning From: lester@lsces.co.uk (Lester Caine) On 27/01/15 10:24, Yasuo Ohgaki wrote: > While I can understand the reason behind opposition, but current web is not > bounded to local country. Most applications today logs time using UTC and > time stamp is converted whatever local time as needed, isn't it? Of course, > it depends on application though. Having UTC as the default makes sense > to me. > > Besides time management best practice, users have learned enough, > haven't them? Best practice when working cross timezones is to store all information as UTC and display using a clients local timezone. It all falls apart when one starts trying to put into practice. Most 'local' PHP installations will be run on machines with their real time clock set to local time. If they are accessed by remote clients, the browsers tz offset will be used in the absence of a real DST correct timezone. Many sites will be using 'seconds' as the time base without knowing if leap seconds are included or not and wondering why things are not quite right. So basically defaulting the majority of PHP installs to UTC is simply wrong, if only because we can't even agree on how UTC is calculated. It was hoped that the new tzdist working group might bring a bit of sanity, but it seems providing a standard to work to is not what any of these working groups is chartered to provide - just rules so that everybody can carry on doing their own thing :( -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk