Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67536 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84187 invoked from network); 27 May 2013 03:31:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 May 2013 03:31:36 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.91 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.91 smtp91.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.91] ([108.166.43.91:48262] helo=smtp91.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8F/4A-32733-793D2A15 for ; Sun, 26 May 2013 23:31:36 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 07B4A140108; Sun, 26 May 2013 23:31:33 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 9DA12140102; Sun, 26 May 2013 23:31:32 -0400 (EDT) Message-ID: <51A2D395.5030302@sugarcrm.com> Date: Sun, 26 May 2013 20:31:33 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "RQuadling@GMail.com" CC: PHP internals References: <51A092FC.4010700@wikimedia.org> <51A1AF3E.5000704@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] date.timezone E_WARNING -- Really necessary? What's the rationale? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > As more and more site/services are being hosted in the cloud, allowing > requests to be handled locally geographically, in different timezones, > does it make ANY sense in setting a timezone at all other than UTC? There's no relation between location of the server/site and the timezone. If your site is meant to serve specific timezone, it makes sense to set it to that timezone. > From what I can see, a server (which may not be under our control) COULD > have pretty much any time and/or timezone on it. So even if we DO set a > timezone in PHP, the time could still be out and that really isn't a > good thing. If you do not control your server, the whole discussion is moot as you can not do anything about TZ settings. > sourced process to determine where in the world the server is (I have > access to servers all over Europe. I don't know the timezones that they > are all in initially and had to work to confirm that the machine TZ setting is not meant to be the timezone the server is physically in. TZ setting is meant to be the timezone that your site is serving. Of course, if the site is meant to serve multiple zones, then UTC may be appropriate. But if your site is a local shop in Elbonia, then all your times would be appropriate to Elbonian timezone, because all activities are done with regard to this timezone. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227