Re: REQUEST_TIME change in PHP 5.4

From: Date: Sat, 24 Dec 2011 14:47:18 +0000
Subject: Re: REQUEST_TIME change in PHP 5.4
References: 1 2 3 4  Groups: php.internals 
Request: Send a blank email to internals+get-57084@lists.php.net to get a copy of this message
On Sat, Dec 24, 2011 at 12:55 PM, Derick Rethans <derick@php.net> wrote: > On Sat, 24 Dec 2011, Pierre Joye wrote: > > > hm, I should read better... > > > > "The REQUEST_TIME value inside server now returns a floating point > number" > > > > How does it break BC except if one is doing a strong type test? which > > makes very little sense in this case. > > > > While a fix is easy, (int) casting and works with all previous > > versions, I would like to know how it breaks apps out there. > > new DateTime("@{$_SERVER['REQUEST_TIME']}"); f.e. > > Yes, this is the one from Zeta Components MvcTools. In eZ Publish it was db based session gc using REQUEST_TIME and compatibility for potential extensions that might have used this variable via eZ Publish api: https://github.com/ezsystems/ezpublish/commit/3483c623769aa9ed3be7b6f33e3579cf8a8efd45 In both cases a (int) was added in front of the variable to make sure it still behaves the same, so not a big deal. But as also mentioned, changes like this requires patching to be compatible with 5.4. So unless this is done to be inline with some standard on such a server variable, I would suggest placing microtime on a separate server variable (since it is indeed useful to have it for time accumulators and performance metrics).

« previous php.internals (#57084) next »