Seaside
Seaside copied to clipboard
Modifies WAServerManager to support subclasses to be defined as default
VAST, and probably other dialects, have a subclass of WAServerManager that is used instead of it.
Since WAServerManager[default]
is a class instance variable, then sending the message default
to WAServerManager
will always answer an instance of itself. Which is more troubling if you access it by means of WAAdmin defaultServerManager
.
This PR modifies the default
class instance variable to be a class variable (named Default
), and provides a beDefault
method that can be used on subclasses to be the "singleton" default.
Out of curiosity, why do you need to subclass WAServerManager
? Is there something we can do so that you don't have to do this?
The WASstServerManager
in VAST provides logging of the start/stop events and also a callback interface (think of an "Announcer") to notify these events to the visual control panel can reflect the state without unnecessary polling.