empire/empserver
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Document blocking constraints.

Browse source
This commit is contained in:
Markus Armbruster 2005-07-01 19:51:00 +00:00
parent 8e8ffb483c
commit 062b50f598
1 changed files with 7 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/clients-howto
View file

@ -53,9 +53,15 @@ Clients should not send overlong or malformed UTF-8 sequences.
A client is called synchronous if it waits for a prompt before it A client is called synchronous if it waits for a prompt before it
sends another line of input. Else it is called asynchronous. sends another line of input. Else it is called asynchronous.
Asynchronous clients must take care to avoid blocking on sending
input. If the client process blocks that way, it can't receive server
output until the server reads more input. That may never happen,
because the server may well block on output, which then deadlocks the
session.
An Empire session consists of two phases: login and playing. An Empire session consists of two phases: login and playing.
emp_client is synchronous during the former and asynchronous during emp_client is synchronous during the former and asynchronous during
the latter. the latter. It can currently deadlock as described above.
Login phase Login phase
----------- -----------