Commit 67682824 authored by Per Cederqvist's avatar Per Cederqvist
Browse files

(Common Types): Mention that times can be expressed in UTC if the

	set-connection-time-format request has been used.
(get-last-text): Ditto.
(set-connection-time-format): Change the status from experimental
	to recommended.
parent a01e85da
......@@ -1547,7 +1547,8 @@ indicated is daylight savings time.
When the server receives a @type{Time} structure from a client it
ignores the @field{day-of-week} and @field{day-of-year} fields.
All times are expressed in the time zone of the server.
All times are expressed in the time zone of the server, unless the
@reqdlink{set-connection-time-format} request is used@linkhere{}.
@subsection Conference Numbers
......@@ -3110,7 +3111,7 @@ their current status.
* find-previous-conf-no:: r Get previous conference number (117)
* get-scheduling:: e Get client priority information (118)
* set-scheduling:: e Alter client priority (119)
* set-connection-time-format:: e Use UTC or local timezone of server? (120)
* set-connection-time-format:: r Use UTC or local timezone of server? (120)
@end menu
......@@ -5989,6 +5990,10 @@ of the server may also have been adjusted manually from time to time.
This protocol specification does not mandate what the server should do
in such cases.
If @reqlink{set-connection-time-format} has been used with
@code{use-utc} set to 1, the @rarg{before} time should be expressed in
UTC. Daylight savings time will not be an issue in that case.
1 58 49 6 22 19 6 97 6 199 1
......@@ -8651,7 +8656,7 @@ different priorities.
@node set-connection-time-format
@section set-connection-time-format [120] (Experimental)
@section set-connection-time-format [120] (Recommended)
@findex set-connection-time-format
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment