The only problem is, that it cant use the timezone_set command.You can request a response back in any date-format you wish, or use the default one given in the function itself.on systems with slow IO like the Windows machine I used 3 years ago.PHP 4 did not produce any log messages, and therefore was as fast as PHP5 with a timezone set.
However, "Date Time Zone::list Identifiers()" can turn a timezone integer into an array of timezone identifier strings.
So, here's my answer: This creates a huge problem for downloadable programs, which obviously cannot be hardcoded as this suggests, since the coder has no idea where they will be run.
Seems to me that if the server's timezone cannot be relied on, then THAT is the the problem which needs fixed.
The 5.2.6 server did 5 times faster with date_default_timezone_set.
As you can see below, the 5.2.6-Windows machine did a LOT faster.