http://bugzilla.lysator.liu.se/show_bug.cgi?id=565
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
OS/Version|Linux |All
Platform|PC |All
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=949
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Target Milestone|--- |Future
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=948
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Priority|P2 |P3
Target Milestone|--- |Future
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=957
------- Additional Comments From byers(a)lysator.liu.se 2003-01-04 21:13 -------
Can't we just make DST go away? Forever and ever and ever?
I think the only reasonable solution is to give clients timestamps in (or based
on) UTC and make them responsible for performing DST calculations.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=957
------- Additional Comments From ceder(a)lysator.liu.se 2003-01-04 21:03 -------
The proposal isn't good enough. It doesn't handle daylight savings time.
If you use get-server-timezone in Sweden in December, you will get 3600
+ 43200. If you do it in July, you will get 2 * 3600 + 43200.
Consider a text written in December, and another written in July. If you
use the offset returned by get-server-timezone to calculate when the texts
were written, expressed in UTC, you will arrive at the wrong time for
one of them. Which one depends on if DST is in effect or not.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=960
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Keywords| |async
Target Milestone|--- |2.1.0
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=960
Summary: New async: timezone offset changed
Product: lyskomd
Version: 2.0.7
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: server
AssignedTo: ceder(a)lysator.liu.se
ReportedBy: ceder(a)lysator.liu.se
QAContact: lyskomd-qa(a)lists.lysator.liu.se
If the timezone offset returned by get-server-timezone (see bug 957)
is changed, an asynchronous message should indicate so. The asynchronous
message should include the new offset.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=959
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Keywords| |newrequest
Target Milestone|--- |2.1.0
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=959
Summary: Report times in UTC, or a timezone of the clients'
choosing
Product: lyskomd
Version: 2.0.7
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: server
AssignedTo: ceder(a)lysator.liu.se
ReportedBy: ceder(a)lysator.liu.se
QAContact: lyskomd-qa(a)lists.lysator.liu.se
Currently, all times are sent in the local time zone of the server. This
leads to problems for some clients (see bug 292).
The request proposed below allows a client to specify which timezone that
should be used. It only affects the current connection.
@node set-connection-timezone
@section set-connection-timezeone [XXX] (Recommended)
@findex set-connection-timezone
@example
set-connection-timezone [XXX] (( use-utc : @lt{BOOL};
offset : @lt{INT32} ))
-> ( );
@end example
This call sets the timezone used when communicating on this connection.
If @rarg{use-utc} is true, UTC will be the time base. Otherwise, the local
time of the server will be the time base.
The @rarg{offset} argument is an additional offset, expressed as seconds
west of the ternational date line (which can also be viewed as seconds west
of GMT plus 43200). The offset is relative the international date line
rather than GMT since the LysKOM protocol does not support signed
integers.
When a new connection is established, it behaves as if
@req{set-connection-timezone} had been called with @rarg{use-utc} set to 0
and @rarg{offset} set to 43200. In other words: all times are reported
in the local timezone of the server.
You don't have to log in to use this request.
@subheading Error codes
- something for offset out of range
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=957
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Keywords| |newrequest
Target Milestone|--- |2.1.0
------- Additional Comments From ceder(a)lysator.liu.se 2003-01-04 18:28 -------
This should be called get-server-timezone.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.