Unified · Split
| @@ -120,20 +120,33 @@ is an empty or · 119 unmodified lines | |||
| 120 | .B nil | 120 | .B nil |
| 121 | string or an explanation of the problem. | 121 | string or an explanation of the problem. |
| 122 | .PP | 122 | .PP |
| 123 | If the client closes the file for reading (writing), the server will receive a | ||
| 124 | .B read | ||
| 125 | .RB ( write ) | ||
| 126 | message with a | ||
| 127 | .B nil | ||
| 128 | .I rc | ||
| 129 | .BI ( wc )\f1. | ||
| 130 | The server can use these signals to determine when to stop processing. | ||
| 131 | The | 123 | The |
| 132 | .I fid | 124 | .I fid |
| 133 | received by the server can be used to manage the multiplexing of multiple | 125 | received by the server can be used to manage the multiplexing of multiple |
| 134 | active clients sharing a single file; see | 126 | active clients sharing a single file; see |
| 135 | .IR intro (5) | 127 | .IR intro (5) |
| 136 | for details. | 128 | for details. |
| 129 | Each distinct | ||
| 130 | open of the file will yield a distinct | ||
| 131 | .IR fid , | ||
| 132 | unique to that open, which will appear in the read and write | ||
| 133 | messages corresponding to reads and writes on that open instance of the file. | ||
| 134 | .PP | ||
| 135 | When the client closes the file, | ||
| 136 | the server will be sent a | ||
| 137 | .B read | ||
| 138 | message with a nil | ||
| 139 | .IR rc , | ||
| 140 | then a | ||
| 141 | .B write | ||
| 142 | message with a nil | ||
| 143 | .IR wc . | ||
| 144 | A server typically ignores the former and uses the latter as a signal to stop processing for the given client | ||
| 145 | (more precisely, the given | ||
| 146 | .IR fid ). | ||
| 147 | Note that the | ||
| 148 | .I fid | ||
| 149 | can later be re-used by another client. | ||
| 137 | .SH SOURCE | 150 | .SH SOURCE |
| 138 | .B /emu/port/devsrv.c | 151 | .B /emu/port/devsrv.c |
| 139 | .br | 152 | .br |