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

(Future changes): Don't mention bugs that are closed. Mention that

	the list of included bugs is incomplete.
(Protocol Version History): Document version 11.
(Document Edition History): Document edition 11.0.
parent db5a30fb
......@@ -10966,14 +10966,6 @@ the @type{Text-Stat}. They should probably be separated from the
which aux-items that exists. (This is
@uref{http://bugzilla.lysator.liu.se/show_bug.cgi?id=135, bug 135}.)
@item
There is too few asynchronous messages. There are many situations
where something can change without a client noticing it.
There is more than one way to fix this, and it is not known which way
is the best. (This is
@uref{http://bugzilla.lysator.liu.se/show_bug.cgi?id=93, bug 93}.)
@item
The super conference is used for two purposes: to indicate where
followups of original conferences should be sent, and to indicate
......@@ -10992,16 +10984,6 @@ The security system is too complex, yet unable to do many useful
things, and should be rethought. (This is
@uref{http://bugzilla.lysator.liu.se/show_bug.cgi?id=137, bug 137}.)
@item
The @reqlink{mark-as-read} call is a reasonably good way to mark a
single text as read (but one could argue that it should take a single
@code{Text-No} and an @code{ARRAY Conf-No} as arguments), but there is
no easy way to undo such an operation. You can use
@reqlink{set-last-read} followed by a number of @req{mark-as-read}
calls to get the desired effect, but it would be nice to have a
@code{mark-as-unread} call. (This is
@uref{http://bugzilla.lysator.liu.se/show_bug.cgi?id=53, bug 53}.)
@item
If the client issues several request without waiting for a reply, the
replies will nevertheless always arrive in the same order as the
......@@ -11021,10 +11003,116 @@ the corresponding call. (This is
For more information about potential future changes, see
@uref{http://bugzilla.lysator.liu.se/, Bugzilla @@ Lysator}.
The above list is in no way complete.
@node Protocol Version History
@appendix Protocol Version History (informative)
@section Protocol version 11 (first implemented in lyskomd 2.1.0)
@table @asis
@item New Server Calls
These new calls have status Recommended.
@itemize @bullet
@item 107=query-read-texts
@item 108=get-membership
@item 109=mark-as-unread
@item 110=set-read-ranges
@item 111=get-stats-description
@item 112=get-stats
@item 113=get-boottime-info
@item 114=first-unused-conf-no
@item 115=first-unused-text-no
@item 116=find-next-conf-no
@item 117=find-previous-conf-no
@item 120=set-connection-time-format
@item 121=local-to-global-reverse
@item 122=map-created-texts-reverse
@end itemize
These new calls have status Experimental.
@itemize @bullet
@item 118=get-scheduling
@item 119=set-scheduling
@end itemize
@item Status change
The following calls have change status from Experimental to Recommended.
@itemize @bullet
@item 105=set-keep-commented
@end itemize
The following calls have changed status from Recommended or
Experimental to Obsolete.
@itemize @bullet
@item 98=query-read-texts-10
@item 99=get-membership-10
@end itemize
@item New and Modified Types
@itemize @bullet
@item Read-Range
@item Membership
@item Membership-Type
@item Stats
@item Stats-Description
@item Static-Server-Info
@item FLOAT
@end itemize
@item New Asynchronous Messages
@itemize @bullet
@item 19=async-new-user-area
@item 20=async-new-presentation
@item 21=async-new-motd
@item 22=async-text-aux-changed
@end itemize
@item New aux-items
@xref{Document Edition History}, as new aux-items are added between
protocol versions.
@item New error codes
@xref{Document Edition History}.
@item Notes
@itemize @bullet
@item The @code{reserved1} bit of
@type{Membership-Type} has been renamed to
@field{passive-message-invert}. @xref{Membership Information}. This
affects @asynclink{async-send-message} and @reqlink{send-message}.
@item The following requests can no longer be used until you have
logged in: @reqlink{get-last-text}, @reqlink{find-next-text-no} and
@reqlink{find-previous-text-no}.
@item You can now modify the type of a recipient with the
@reqlink{add-recipient} call if you are the supervisor of either the
author, recipient or sender. The check used to be more restrictive.
@item The following asynchronous messages are also sent to recipients
of texts linked to the relevant text via comment or footnote links:
@asynclink{async-new-text-old}, @asynclink{async-deleted-text},
@asynclink{async-new-text}, @asynclink{async-new-recipient} and
@asynclink{async-sub-recipient}.
@end itemize
@end table
@section Protocol version 10 (first implemented in lyskomd 2.0.0)
@table @asis
......@@ -11323,6 +11411,103 @@ All calls from 0--56.
@table @asis
@item 11.0: 2003-08-FIXME
@emph{New aux-items:} @aux{mx-refuse-import} [35]. @xref{Aux-Item
Types}.
@emph{New types:} @type{Read-Range} and @type{Membership} (the old
@type{Membership} was renamed to @type{Membership-10}).
@xref{Membership Information}.
@type{Stats} and @type{Stats-Description}. @xref{Statistics}.
@type{Static-Server-Info}. @xref{Server Information}.
@type{FLOAT}. @xref{Simple Data Types}.
@emph{Status change:} The @reqlink{query-read-texts-10} and
@reqlink{get-membership-10} requests are now obsolete. The
@reqlink{set-keep-commented} request is now recommended.
@emph{New calls:}
@itemize @bullet
@item @reqlink{query-read-texts}
@item @reqlink{get-membership}
@item @reqlink{mark-as-unread}
@item @reqlink{set-read-ranges}
@item @reqlink{get-stats-description}
@item @reqlink{get-stats}
@item @reqlink{get-boottime-info}
@item @reqlink{first-unused-conf-no}
@item @reqlink{first-unused-text-no}
@item @reqlink{find-next-conf-no}
@item @reqlink{find-previous-conf-no}
@item @reqlink{get-scheduling}
@item @reqlink{set-scheduling}
@item @reqlink{set-connection-time-format}
@item @reqlink{local-to-global-reverse}
@item @reqlink{map-created-texts-reverse}
@end itemize
@emph{New error codes:} @errorcode{invalid-range},
@errorcode{invalid-range-list}, @errorcode{priority-denied},
@errorcode{weight-denied}, @errorcode{weight-zero} and
@errorcode{undefined-measurement}.
@emph{New async messages:}
@itemize @bullet
@item @asynclink{async-new-user-area}
@item @asynclink{async-new-presentation}
@item @asynclink{async-new-motd}
@item @asynclink{async-text-aux-changed}
@end itemize
@emph{Protocol change:} Renamed the @code{reserved1} bit of
@type{Membership-Type} to @field{passive-message-invert}.
@xref{Membership Information}. This affects
@asynclink{async-send-message} and @reqlink{send-message}.
The following requests can no longer be used until you have logged in:
@reqlink{get-last-text}, @reqlink{find-next-text-no} and
@reqlink{find-previous-text-no}.
You can now modify the type of a recipient with the
@reqlink{add-recipient} call if you are the supervisor of either the
author, recipient or sender. The check used to be more restrictive.
Aux-item tags 10200-10299 are now reserved for private test use.
@xref{Client-Specific Aux-Item Types}.
The following asynchronous messages are also sent to recipients of
texts linked to the relevant text via comment or footnote links:
@asynclink{async-new-text-old}, @asynclink{async-deleted-text},
@asynclink{async-new-text}, @asynclink{async-new-recipient} and
@asynclink{async-sub-recipient}.
Two requests can now return more error codes than they used to:
@table @asis
@item @reqlink{add-comment}
@errorcode{already-comment} and @errorcode{already-footnote}.
@item @reqlink{add-footnote}
@errorcode{already-comment}.
@end table
The field @code{later-texts-exists} in @type{Text-Mapping} has been
renamed to @field{more-texts-exists}, as this name is more meaningful
for the new requests @reqlink{local-to-global-reverse} and
@reqlink{map-created-texts-reverse}.
@emph{Fixed errors:} The description of the error
@errorcode{index-out-of-range} was wrong for
@reqlink{add-footnote},missing for @reqlink{create-person-old},
@reqlink{create-person}, @reqlink{create-conf-old},
@reqlink{create-conf} and @reqlink{create-text-old}, and incomplete
for @reqlink{create-text}.
@asynclink{async-leave-conf} is not sent when the person is deleted,
so don't say that it is.
@item 10.7: 2002-11-03
@emph{Fixed errors:} The description of common block of the user area
......
Markdown is supported
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