Client side shutdown.

R. Clayton (rclayton@monmouth.edu)
(no date)

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: R. Clayton: "sRPC questions."
• Previous message: R. Clayton: "Project 2 reminder."
• In reply to: R. Clayton: "When is a Tuesday not a Tuesday?"

      call shutdown
      out emsg

   When a sRPC client calls this function, does it have to get emsg from
   server?

It depends on how you implement your system (and sRPC protocol in particular).
If you have a stateless implementation (which implies UPD), then the
client-side probably won't need to communicate with the server-side. If you
have a stateful implementation (required if you use TCP), then the client-side
needs to communicate with the server-side, and that may result in error
messages.

As an aside, client-side shutdown error messages don't have come from the
server side. If sRPC-user code calls shutdown twice on the same instance, the
second call should result in an error message. Such an error message cannot
have come from a server side, because the instance no longer has a connection
to a server.

Also, both the client- and server-side provide a shutdown message to sRPC-user
code; if you wanted to, you could ask the same question about the server side
(and get the same answer).

• Next message: R. Clayton: "sRPC questions."
• Previous message: R. Clayton: "Project 2 reminder."
• In reply to: R. Clayton: "When is a Tuesday not a Tuesday?"

This archive was generated by hypermail 2.0b3 on Tue May 06 2003 - 14:00:05 EDT