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@lysator.liu.se ReportedBy: ceder@lysator.liu.se QAContact: lyskomd-qa@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.