Extensibility

HostedStore was designed with modification capability as a top priority. Because every need cannot be anticipated, the goal was to create an application that had plenty of features to satisfy the needs of most stores while providing the means for developers to easily modify and extend the default core functionality. In addition to open store template and content page format files, a series of hook point variables and hook point format files were created for this specific purpose.

Hook point variables serve different functions. One type can be used to disable specific pieces of the core HostedStore code. Another type, when set, checks for a specific format file and, if present, inserts the code in the file directly into HostedStore's core code. There are also global hook points that are always called for cases where a piece of code is always used. A different approach to the shopping cart is an example of a perfect use for a global hook point.

Code can be directly inserted into the hook point format files or the code can be called from an entirely different format file or LassoApp. The latter method is suggested in order to make it easy for several modules to be use the same hook point with the minimum possibility of adversely affecting the code of another module.

The two types of hook point variables can be used separately or combined for more complex functionality. For example, in some cases there may be a need to do some additional data processing in addition to the processing already performed by HostedStore. In that case, the new code can be inserted before or after the specific code block depending on if pre or post processing is needed. Suppose the existing product search code does not satisfy the needs of a store. Hook point variables can be combined to disable the product search code block and insert a new version written by the developer.

There is a lot of power granted to developers through the hook point interface. If a hook point or hook point variable is needed, but not currently available, then be sure to request that it is added in a future release. Anticipating all of the ways a developer may want to extend HostedStore is difficult so a code block that should have been exposed may have been overlooked. Frequent releases are planned to add new functionality so if the modification request is reasonable the wait time should be minimal.

It is hoped that developers who have created general purpose modules will make the modules available to other HostedStore users either for a fee or for free. A module directory is provided so that modules meant for public consumption can be found in one central location. Third party module vendors are encouraged to publish how their module affects the code in HostedStore so maximum module compatibility and interoperability can be ensured.