(Server Information): Refer to find-previous-conf-no.

(find-next-conf-no): New request.
(find-previous-conf-no): New request.

doc/Protocol-A.texi

@@ -2147,8 +2147,8 @@ with @code{what} set to @code{persons}@linkhere{}.)
 @item highest-conf-no
 The highest conference number that existed on startup.  (To find the
 highest conference number that exists right now, use the
-@reqlink{first-unused-conf-no} and subtract 1.)
-@c FIXME (bug 123): refer to get-previous-conf.
+@reqlink{first-unused-conf-no} and @reqlink{find-previous-conf-no}
+calls.)
 
 @end table
 
@@ -3078,6 +3078,8 @@ their current status.
 * get-boottime-info::           r Get server startup status information   (113)
 * first-unused-conf-no::        r Get first unused conference number      (114)
 * first-unused-text-no::        r Get first unused text number            (115)
+* find-next-conf-no::           r Get next conference number              (116)
+* find-previous-conf-no::       r Get previous conference number          (117)
 @end menu
 
 @ifnottex
@@ -8397,6 +8399,90 @@ This call always succeeds
 
 
 
+@node find-next-conf-no
+@section find-next-conf-no [116] (11) Recommended
+
+@findex find-next-conf-no
+@example
+        find-next-conf-no [116] ( start : @lt{Conf-No} )
+                -> ( @lt{Conf-No} );
+@end example
+
+This call returns the next conference that you are allowed to see in
+the database created after conference @rarg{start}.  @rarg{start} does
+not have to be a valid or readable conference number, as shown in the
+examples.
+
+@reqexample
+@example
+        1 116 0
+        @t{=1 2}
+        1 116 2
+        @t{=1 4}
+@end example
+
+This example shows how to retrieve the first readable conference in
+the LysKOM database by calling @req{find-next-conf-no} with
+@rarg{start} set to zero.  In the example, the first conference is number 2.
+The second example gets the conference following number 2, which happens to
+be conference number 4.
+
+@subheading Error codes
+
+@table @errorcode
+
+@item login-first
+Login required before issuing this call.
+
+@item undefined-conference
+There is no conference following conf @rarg{start}.
+@end table
+
+
+@node find-previous-conf-no
+@section find-previous-conf-no [117] (11) Recommended
+
+@findex find-previous-conf-no
+@example
+        find-previous-conf-no [117] ( start : @lt{Conf-No} )
+                -> ( @lt{Conf-No} );
+@end example
+
+This call returns the last accessible conference in the database
+created before @rarg{start}.  @rarg{start} does not have to be a valid
+or readable conference number, as shown in the examples.
+
+@reqexample
+@example
+        1 114
+        @t{=1 12345}
+        2 117 12345
+        @t{=2 12330}
+        1 117 12330
+        @t{=1 12329}
+@end example
+
+This example uses @reqlink{first-unused-conf-no} to find the largest
+number that can meaningfully be sent to @req{find-previous-conf-no}.
+It then uses the request twice to find that the two conferences with
+highest conference numbers that are accessible to the user logged in
+is 12329 and 12330.
+
+@subheading Error codes
+
+@table @errorcode
+
+@item login-first
+Login required before issuing this call.
+
+@item undefined-conference
+There is no conf preceding conf @rarg{start}.
+@end table
+
+
+
+
+
 @node Asynchronous Messages
 @chapter Asynchronous Messages