On 6/10/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I agree with Tijnema he's hit the nail on the head. And the inability to handle
daylight time really is a big potential snag - who in North America isn't on
daylight time at some point in the year? If the timezone data is unreliable
then
Stefanos Harhalakis wrote:
On Sunday 10 June 2007, Richard Lynch wrote:
On Sat, June 9, 2007 8:06 am, Stefanos Harhalakis wrote:
Timezone: +0200
that will specify their timezone offset. This way scripts will be able
to
provide appropriate date/time strings/representations and/or content.
On Monday 11 June 2007 16:05, Lester Caine wrote:
Timezone information is only of use for the CURRENT day - even if it is
wrong. It is ESSENTIAL that any changes also include the daylight saving
information. Since this is not included, all current sites handling event
related information in
Stefanos Harhalakis wrote:
On Monday 11 June 2007 16:05, Lester Caine wrote:
SNIP - misses the point!!!
Hope this clears things a bit...
As I actually USE a clients time offset, I know what the problem is. The DATA
is ALL stored as UTC time data, so it does not matter who enters it. It
On 6/11/07, Stefanos Harhalakis [EMAIL PROTECTED] wrote:
On Monday 11 June 2007 16:05, Lester Caine wrote:
snip
By the way, what makes you think that most people have an invalid timezone
configured? Windows XP have NTP support that is enabled by default. Without a
proper timezone this should
On Monday 11 June 2007 18:15, Lester Caine wrote:
calender of events over a change in daylight saving I NEED to know !!!
I believe that I finally understand your thoughts. You mean that you need to
use the timezone information to know when in the future the time will change
(or in the past).
Stefanos Harhalakis wrote:
On Monday 11 June 2007 18:15, Lester Caine wrote:
calender of events over a change in daylight saving I NEED to know !!!
I believe that I finally understand your thoughts. You mean that you need to
use the timezone information to know when in the future the time
On Mon, June 11, 2007 9:05 am, Stefanos Harhalakis wrote:
There is no need to include the DST information since when on DST
the client
will be sending the propper offset. For example, EET+2EEST is +0200
during
winter and +0300 during DST.
I think you are over-simplifying things too much...
On Sunday 10 June 2007, Tijnema wrote:
On 6/9/07, Richard Lynch [EMAIL PROTECTED] wrote:
On Sat, June 9, 2007 8:06 am, Stefanos Harhalakis wrote:
Timezone: +0200
that will specify their timezone offset. This way scripts will be able
to
provide appropriate date/time
2007 03:15:33 +0300
CC: php-general@lists.php.net
Subject: Re: [PHP] [RFC] HTTP timezone
On Sunday 10 June 2007, Richard Lynch wrote:
On Sat, June 9, 2007 8:06 am, Stefanos Harhalakis wrote:
Timezone: +0200
that will specify their timezone offset. This way scripts will be able
to
provide
On Sunday 10 June 2007, Tijnema wrote:
To get back to the point, I think that the timezone should be defined
on what time it actually is at his PC, and what time it is on
time.nist.gov for example, and not lookng at some setting... Timezone
setting is often wrong, people just update their time
On 6/10/07, Stefanos Harhalakis [EMAIL PROTECTED] wrote:
On Sunday 10 June 2007, Tijnema wrote:
To get back to the point, I think that the timezone should be defined
on what time it actually is at his PC, and what time it is on
time.nist.gov for example, and not lookng at some setting...
I agree with Tijnema he's hit the nail on the head. And the inability to handle
daylight time really is a big potential snag - who in North America isn't on
daylight time at some point in the year? If the timezone data is unreliable
then no thinking developer will use it. The question then
Hello there,
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
On 6/9/07, Stefanos Harhalakis [EMAIL PROTECTED] wrote:
Hello there,
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:
On Saturday 09 June 2007, Daniel Brown wrote:
On 6/9/07, Stefanos Harhalakis [EMAIL PROTECTED] 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
Stefanos Harhalakis wrote:
On Saturday 09 June 2007, Daniel Brown wrote:
On 6/9/07, Stefanos Harhalakis [EMAIL PROTECTED] 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.
On Saturday 09 June 2007, Stut wrote:
Just wanted the opinion of PHP people/developers since PHP programmers
will be most affected by this. Can you point me to the proper php related
list to ask?
I fail to see how PHP programmers will be most affected by this since
it would equally
Stefanos Harhalakis wrote:
On Saturday 09 June 2007, Stut wrote:
Just wanted the opinion of PHP people/developers since PHP programmers
will be most affected by this. Can you point me to the proper php related
list to ask?
I fail to see how PHP programmers will be most affected by this since
On Saturday 09 June 2007, Stut wrote:
Stefanos Harhalakis wrote:
I meant people using PHP to write programs also. I would dispute your
assertion that the majority of dynamic web pages are written in PHP. I
would accept an assertion that PHP is one of the most widely used
languages for web
On Sat, June 9, 2007 11:08 am, Stut wrote:
Stefanos Harhalakis wrote:
On Saturday 09 June 2007, Daniel Brown wrote:
On 6/9/07, Stefanos Harhalakis [EMAIL PROTECTED] wrote:
I'm currently writting and Internet Draft candidate to describe
an HTTP
header that will be used to transfer
On Sat, June 9, 2007 12:02 pm, Stefanos Harhalakis wrote:
I've already thought about providing the full time but I didn't find
any
applications. Can you provide some examples about its usage? How can
you tell
whether a user has wrong time and not wrong timezone?
You can't.
You can't tell
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
On 6/9/07, Richard Lynch [EMAIL PROTECTED] 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
On Sunday 10 June 2007, Richard Lynch wrote:
On Sat, June 9, 2007 8:06 am, Stefanos Harhalakis wrote:
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
On Sat, June 9, 2007 7:15 pm, Stefanos Harhalakis wrote:
On Sunday 10 June 2007, Richard Lynch wrote:
On Sat, June 9, 2007 8:06 am, Stefanos Harhalakis wrote:
Timezone: +0200
that will specify their timezone offset. This way scripts will be
able
to
provide appropriate date/time
:15:33 +0300
CC: php-general@lists.php.net
Subject: Re: [PHP] [RFC] HTTP timezone
On Sunday 10 June 2007, Richard Lynch wrote:
On Sat, June 9, 2007 8:06 am, Stefanos Harhalakis wrote:
Timezone: +0200
that will specify their timezone offset. This way scripts will be able
to
provide
27 matches
Mail list logo
