[prev in list] [next in list] [prev in thread] [next in thread] 

List:       php-general
Subject:    Re: [PHP] [RFC] HTTP timezone
From:       Tijnema <tijnema () gmail ! com>
Date:       2007-06-09 22:21:25
Message-ID: d8269d910706091521v4a46e63cu8cddf6f60839b38b () mail ! gmail ! com
[Download RAW message or body]

On 6/9/07, Richard Lynch <ceo@l-i-e.com> wrote:
> On Sat, June 9, 2007 8:06 am, Stefanos Harhalakis wrote:
> >   I'm currently writting and Internet Draft candidate to describe an
> > HTTP
> > header that will be used to transfer timezone information from
> > browsers to
> > servers. Compliant browsers will need to send a timezone string:
> >
> > Timezone: +0200
> >
> > that will specify their timezone offset. This way scripts will be able
> > to
> > provide appropriate date/time strings/representations and/or content.
>
> It's pretty useless and unreliable since user's clocks/timezone
> settings are incorrect far too often...
>
> YMMV

I agree with you, clock settings are incorrect way too often, I just
checked my own, and I see that the time is correct, but the Timezone
is at GMT, while i live in GMT+1, but in summer, it's GMT+2.
That brings me to the next point, what about DST?
I've read your complete draft, and it doesn't say anything about DST,
What should browsers send for my country? +0100 or +0200?

Tijnema

Ps. what's the next thing we send to the browser? We already sent a
lot of info through the user-agent header... Next year we send our
computers specs to the server so that we get a site that is made for
the performance of our computer?

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[prev in list] [next in list] [prev in thread] [next in thread]