Server Smalltalk Guide

Packaged image exits

Packaged images have the following cycle:

  1. Do image startup.
  2. Execute the startup code.
  3. Exit image.

If possible, it's usually best to have your server application run in the starting process. But startup code commonly forks a new process to do the server processing. The starting process then resumes execution and exits the image.

The solution is to terminate the starting process after starting the server. This is done by setting the startup code as follows:

foo bar. 
Processor activeProcess basicTerminate
Tip icon
Use basicTerminate with headless images (images without a UI). Using terminate causes another UIProcess to be started. This causes a walkback as it attempts to start the UI message loop, which will not have been packaged. For headed images you should use terminate.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]