Startup and shutdown
Many objects within the system require a coordinated startup and shutdown procedure. To facilitate this, SST adopts a standard set of methods and defines when they are executed and what they should do. The startUp methods (in the IuSstStartable interface) are:
startUp
Starts the receiver. In general this means starting related processes, allocating resources and building interobject links. Once startUp has completed the receiver is ready to fulfill its prescribed role.
shutDown
Stops the receiver. In general this means stopping related processes, releasing allocated resources and removing some interobject links. An object which has been shutDown can typically be restarted using startUp though it may not restart with exactly the same behavior as before it was shutDown.
clear
Ensures that the receiver is shutDown and then clear out its instance variables such that no dangling pointers to complex objects remain. startUp cannot be sent to the receiver once it has been cleared.
The startUp and shutDown methods are not related to the normal VA Smalltalk application startup and shutdown protocol. That is, they are not called automatically on image startup and shutdown.
HTTP server access log
An SST HTTP server can write an "access" log containing an entry for each request received by the server. Entries in the log are formatted according to the default format used by the Apache HTTP server in order to enable tooling for Apache logs to be used for SST logs as well.
1. The access log is initialized in SstHttpServer>>startUp. If an access log is desired, it can be specified in 2 ways:
2. The application can send SstHttpServer>>accessLogFormatPolicy: AND SstHttpServer>>accessLog: prior to sending
Last modified date: 07/06/2018