Server Smalltalk Guide
Invocation handlers manage operating system resources--such as
communications transports--and the active nature of the distributed
system, whether or not the handler is running. On startup the handler
must ensure that any OS resources are invalidated, and that, if desired, it be
restarted in a running state. The following are the valid mode settings
for invocation handler restart:
- SstCleanUpMode
- Stops the handler such that no information is lost but all related
processes and OS resources are deleted. See
basicShutDown.
- SstRemoveMode
- Runs SstTerminateMode but also removes the handler from the
system.
- SstRestartMode
- Runs SstCleanUpMode and restarst the handler using the normal
startUp procedure. Processes waiting for replies are not
killed.
- SstTerminateMode
- Runs SstCleanUpMode but also runs basicTerminate on
any processes waiting for replies. See
clearPendingRepliesWith:.
- SstTerminateRestartMode
- Runs SstTerminateMode and restarts the handler using the normal
startUp procedure.
If you are not using one of the terminate modes, you should ensure that any
processes waiting for replies actually get replies. Otherwise, they
will block forever. There may be application logic to justify this or
you can use clearPendingRepliesWith: explicitly after image
startup.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]