diff options
| author | forsyth <forsyth@vitanuova.com> | 2010-02-02 17:06:56 +0000 |
|---|---|---|
| committer | forsyth <forsyth@vitanuova.com> | 2010-02-02 17:06:56 +0000 |
| commit | 1a4a30605f5c1b0911e5a278190e347a5a092fdd (patch) | |
| tree | 5991afb21163a8a6e1570217903e51b20fda463e /man/5/flush | |
| parent | 9d5057f4014d21d559fd83d5e6c4352fc930b877 (diff) | |
20100202-1706
Diffstat (limited to 'man/5/flush')
| -rw-r--r-- | man/5/flush | 27 |
1 files changed, 25 insertions, 2 deletions
diff --git a/man/5/flush b/man/5/flush index 48c2d306..914f81d7 100644 --- a/man/5/flush +++ b/man/5/flush @@ -24,7 +24,7 @@ The semantics of .B flush depends on messages arriving in order. .PP -The server must answer the +The server should answer the .B flush message immediately. If it recognizes @@ -46,6 +46,29 @@ can never be responded to by an .B Rerror message. .PP +The server may respond to the pending request before +responding to the +.BR Tflush . +It is possible for a client to send multiple +.B Tflush +messages for a particular pending request. Each +subsequent +.B Tflush +must contain as +.I oldtag +the tag of the pending request (not a previous +.BR Tflush ). +Should multiple +.BR Tflush es +be received for a pending request, they must be answered in +order. An +.B Rflush +for any of the multiple +.BR Tflush es +implies an answer for all previous ones. Therefore, should +a server receive a request and then multiple flushes for that +request, it need respond only to the last flush. +.PP When the client sends a .BR Tflush , it must wait to receive the corresponding @@ -75,4 +98,4 @@ flushing a .BR Tflush , and flushing an invalid tag. .SH SEE ALSO -.IR sys-read (2). +.IR sys-read (2) |