Ilia Alshanetsky wrote:
I think the REQUEST_TIME semantics of returning float should remain as is.
-1 for adding further environment variables.
A proper explanation of why you take that attitude would be helpful. Personally
I expect REQUEST_TIME to be in the same resolution as the http format time
stamps which does not include milliseconds
(http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.3.1). Personally
DATE is a floating point value with the fractional part being the fraction of
the day. So adding another variation to cope with does not make any sense. So
adding a non-standard environment variable for those who want it rather than
screwing up the existing one is the logical approach?
On Tue, Dec 27, 2011 at 7:52 AM, Derick Rethans<der...@php.net> wrote:
On Tue, 27 Dec 2011, Pierre Joye wrote:
On Tue, Dec 27, 2011 at 1:19 PM, Derick Rethans<der...@php.net> wrote:
Ah, that one. I got lost between all the commas and thought he meant an
RFC for changing REQUEST_TIME from int to float :-)
Which name should we use?
a) REQUEST_TIME_FLOAT
b) REQUEST_TIME_MSEC
c) other?
I'd vote for a (REQUEST_TIME_FLOAT), as MSEC is not what it really does.
Depending on the time and precision it might not show miliseconds f.e.
--
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//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
