Re: date.timezone E_WARNING -- Really necessary? What's the rationale?
| From: | Lester Caine | Date: | Sun, 26 May 2013 11:50:25 +0000 |
| Subject: | Re: date.timezone E_WARNING -- Really necessary? What's the rationale? | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-67529@lists.php.net to get a copy of this message | ||
Richard Quadling wrote:
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?This is something I have been saying all along. The whole thing is broken anyway since you have no idea what time-zone a USER is accessing from since the browser bodge only provides a current time offset. Until a user logs into a site and provides the data of their current daylight saving 'location' anything else is a guess. If you are assuming a server is in a single time-zone, then it makes even less sense to use anything other than UTC and ignore timezones altogether? -- 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