HotSpot: Application architecture

Description

The Hooks and HotSpots in this HotSpot are all related to the general architecture of applications developed using the SalesPoint Framework. They deal with the main architectural notions: the Shop and SalesPoints.

HotSpots

Persistance	Hooks related to making persistent the state of the application.
Shutdown	Hooks related to application shutdown.
Time management	The Hooks in this HotSpot describe how the Shop manages time and how these mechanisms can be adapted and used.

Hooks

Add a new point of sale	A point of sale must be added to the Shop as a point of interaction with the application.
Incorporate new Shop	An instance of a new subclass of the sale.Shop class is needed to replace the default, because some new behavior was added in the subclass; e.
React To Changes In Object's State	An object's state must be monitored and reactions to changes of the object's state must be implemented.
React to Adding or Removing Of SalesPoint	A reaction is necessary, whenever a SalesPoint is added to, or removed from, the Shop.
Specify a transactional context for a point of sale	Processes executed on a SalesPoint are to run in a specific transactional context.