R. Clayton (rclayton@monmouth.edu)
(no date)
The generic shutdown call ends an sRPC session. But in Comer and Stevens'
dictionary service description, there is a quit call. I cannot distinguish
between shutdown() and quit() because both are going to end the connection.
They have two different names, so I'm not understanding how you can't
distinguish between them. But you're confusing two issues. quit() is part of
the Comer-Stevens dictionary (CSD); what quit does depends entirely on the CSD
developer and has no more effect on the sRPC run-time than does any other call
in the CSD (which is not to say that quit() couldn't affect the sRPC session;
it could, for example, call shutdown()). shutdown() is part of the sRPC
run-time system; how it behaves depends only on how you've implemented the
run-time system.
Calling shutdown() disconnects from server and keep on executing local code;
calling quit() disconnects from server and keeps executing local code. On
the server side both calls result in disconnection and release of the
resource. One possibility could be yes, it is same thing named differently.
Another possibility could be no, shutdown() disconnects and keeps on running
and quit() disconnects and finishes the program. Which of this going to be?
It should be clear that calling shutdown() on a sRPC endpoint should not end
the program, so your first possibility is unacceptable. As for your second
possibility, you might find it helpful to review your readings in Chapter 23.
Pay particular attention to Sections 23.5 through 23.7.
This archive was generated by hypermail 2.0b3 on Tue Apr 06 2004 - 13:30:06 EDT