1392 |
such places need to be rewritten in a different way (for example using |
such places need to be rewritten in a different way (for example using |
1393 |
extra threads). |
extra threads). |
1394 |
|
|
1395 |
|
\begin{comment} |
1396 |
|
What happens if a client does not go into the receive phase after a |
1397 |
|
send, but instead does another send, and another one, quickly many |
1398 |
|
sends, as fast as possible? A carelessly written server might |
1399 |
|
create worker threads for each request. Instead, the server should |
1400 |
|
probably reject to accept a request from a client thread that |
1401 |
|
already has a pending request, so the number of worker threads is |
1402 |
|
limited to the number of client threads. |
1403 |
|
|
1404 |
|
This also makes interrupting an RPC operation easier (the client |
1405 |
|
thread ID can be used to identify the request to interrupt). |
1406 |
|
\end{comment} |
1407 |
|
|
1408 |
|
|
1409 |
\subsection{Notifications} |
\subsection{Notifications} |
1410 |
|
|