Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
lyskom-server-ceder-1616-generations-topgit
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Per Cederqvist
lyskom-server-ceder-1616-generations-topgit
Commits
d4ae2c37
Commit
d4ae2c37
authored
May 05, 2001
by
Per Cederqvist
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
(Client-Server Dialog): Markup fixes.
(Future changes): Markup fixes.
parent
7218f408
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
9 deletions
+7
-9
doc/Protocol-A.texi
doc/Protocol-A.texi
+7
-9
No files found.
doc/Protocol-A.texi
View file @
d4ae2c37
...
...
@@ -2,8 +2,6 @@
@c
@c FIXME: Things ceder are about to fix:
@c FIXME:
@c FIXME: move "Error Codes" and "Special Errors" into "Client-Server Dialog"
@c FIXME: error-reply defined twice (conflicting).
@c FIXME: sentence-end-double-space!
@c FIXME: "Foo bar (bar baz.)" or "Foo bar (bar baz)."?
@c FIXME: split "LysKOM Data Types"
...
...
@@ -24,7 +22,7 @@
@c FIXME: "Review the last N by FOO to BAR" is empty
@c FIXME: "Remote control" contains no information
@c
@c
$
Id: Protocol
-
A.texi,v
1
.
14
0
2001
/
05
/
05
07
:
38
:
55
ceder Exp
$
@c
$
Id: Protocol
-
A.texi,v
1
.
14
1
2001
/
05
/
05
08
:
28
:
13
ceder Exp
$
@c
%**start of header
@setfilename protocol-a.info
@settitle LysKOM Protocol A
...
...
@@ -1370,13 +1368,13 @@ spaces and terminating all requests with a linefeed character. The
unless the client follows this requirement.
The server may return two different types of errors. Normal
@
typ
e
{
error-reply
}
errors are replies to syntactically correct calls
to the server, while @
typ
e
{
protocol-error
}
are replies to syntactically
@
cod
e
{
error-reply
}
errors are replies to syntactically correct calls
to the server, while @
cod
e
{
protocol-error
}
are replies to syntactically
incorrect calls. @xref
{
Protocol Error Messages
}
, for more information
about @
typ
e
{
protocol-error
}
.
about @
cod
e
{
protocol-error
}
.
If a call cannot complete successfully, LysKOM will respond with an
@
typ
e
{
error-reply
}
. The meaning of @field
{
error-code
}
and
@
cod
e
{
error-reply
}
. The meaning of @field
{
error-code
}
and
@field
{
error-status
}
varies depending on the request; see @ref
{
Error
Codes
}
, and the documentation for each call, for a list of available
@field
{
error-code
}
values and what they mean.
...
...
@@ -9052,11 +9050,11 @@ read texts.
@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
@
type
{
Text-No
}
and an @typ
e
{
ARRAY Conf-No
}
as arguments), but there is
@
code
{
Text-No
}
and an @cod
e
{
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
@
samp
{
mark-as-unread
}
call.
@
code
{
mark-as-unread
}
call.
@item
If the client issues several request without waiting for a reply, the
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment