Commit 6ae244a2 authored by Per Cederqvist's avatar Per Cederqvist

This is revision 10.1 of the specification.

(Overview): Protocol versions never have a suffix.
(Document Revision History): Wrote entry for 10.1.
(Name Expansion): Regexps are case sensitive.
(re-lookup-person): Tempus changed.
(re-lookup-conf): Tempus changed.
(re-z-lookup): Regexps are case sensitive.
parent 9484d2b4
......@@ -2,7 +2,7 @@
@c
@c FIXME: Explain how the garb works with nice and keep-commented
@c
@c $Id: Protocol-A.texi,v 1.83 1999/07/07 07:44:16 kent Exp $
@c $Id: Protocol-A.texi,v 1.84 1999/07/10 23:07:36 ceder Exp $
@c %**start of header
@setfilename protocol-a.info
@settitle LysKOM Protocol A
......@@ -19,7 +19,7 @@
@end iftex
@ifinfo
This is specification 10.0 of LysKOM Protocol A. It specifies version
This is specification 10.1 of LysKOM Protocol A. It specifies version
10 of the protocol.
Copyright @copyright{} 1995-1999 Lysator ACS.
......@@ -65,7 +65,7 @@ another language under the same conditions as for modified versions.
@top LysKOM Protocol A
This document specifies version 10 of LysKOM Protocol A.
This is revision 10.0 of the specification.
This is revision 10.1 of the specification.
@menu
* Overview::
......@@ -94,7 +94,7 @@ Computing Society and distributed under conditions of the GNU Public
License. LysKOM and its documentation is provided ``as is'' without
warranty of any kind.
This document specifies version 10.0 of protocol A used between a LysKOM
This document specifies version 10 of protocol A used between a LysKOM
client and a LysKOM server. Anything described here as ``unspecified''
is liable to change in future protocol versions.
......@@ -134,13 +134,16 @@ The LysKOM developers can be reached by email to
@table @asis
@item 10.0: 1999-06-31
@item 10.1: 1999-07-12
Call @code{sub-comment} was incorrectly marked obsolete. This has been
corrected.
corrected. Regexps are case sensitive.
@item 10.0: 1999-06-27
The specification was translated to English and converted to Texinfo by
David Byers. Protocol version 10. Distributed with lyskomd 2.0.0.
Note: this revision incorrectly marked the @code{sub-comment} call as
obsolete, and stated that regexp lookup was case insensitive. Both
statements were wrong, and has since been fixed.
@item 9.0: 1996-08-04
Protocol version 9. Distributed with lyskomd 1.9.0.
......@@ -2798,7 +2801,7 @@ or KOM conventions.
This type of expansion, used by the @pxref{re-z-lookup} call and its
predecessors simply matches @code{ed}(1) style regular expressions to
names in the database to find the list of matching names. The matching
is done without regard for character case.
is case sensitive.
@subsection KOM Conventions
......@@ -5964,8 +5967,8 @@ The session @code{session-no} does not exist.
@end example
This call is obsolete. It has been replaced by @pxref{re-z-lookup}. It
used to return a list of persons matching the regular expression
@code{regexp}. The regexp syntax used was that of the @code{ed}(1) Unix
returns a list of persons matching the regular expression
@code{regexp}. The regexp syntax used is that of the @code{ed}(1) Unix
utility.
@unnumberedsubsec Error codes
......@@ -5987,8 +5990,8 @@ not a correct regexp.
@end example
This call is obsolete. It has been replaced by @pxref{re-z-lookup}. It
used to return a list of conferences matching the regular expression
@code{regexp}. The regexp syntax used was that of the @code{ed}(1) Unix
returns a list of conferences matching the regular expression
@code{regexp}. The regexp syntax used is that of the @code{ed}(1) Unix
utility.
@unnumberedsubsec Error codes
......@@ -6273,7 +6276,7 @@ works.
2 74 2H.* 0 1
@t{=1 2 @{ 15HTest Conference 0000 10}
@t{ 21HTrains (-) Discussion 0000 11@}}
3 74 4HT.*C 1 1
3 74 4HT.*[cC] 1 1
@t{=3 2 @{ 15HTest Conference 0000 10}
@t{ 21HTrains (-) Discussion 0000 11@}}
@end example
......@@ -6284,7 +6287,7 @@ two conferences and two persons. The second example uses the same
regular expression, but in this case, the call specifies that the
result is only to contain conferences, so the two persons are not
returned. The third example simply returns all names matching the
pattern ``T.*C''.
pattern ``T.*[cC]''.
@unnumberedsubsec Error codes
......
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