WebsydianExpress - Callback Point

ApplicationServiceEnd

Type

Global callback point implemented by the WebsydianExpress runtime.

Note that changing the callback functions for a global callback point impacts all the sites.

When is the callback point called

ApplicationServiceEnd is called when the Application Service jobs terminates.

At this point no more requests will be handled.

How does the callback point influence later functionality

The callback functions for this callback point can't influence the following functionality.

Errors returned in *Returned Status are disregarded by the callback point.

Example of use

The most common use of this callback point is to perform any clean-up processing that must be done before the Application Service terminates.

For example, if the application needs to connect to a backend ERP system, we have found that it often takes so long establish this connection, that it is not practical to do so for each request. In most cases you would establish this connection in the ApplicationServiceStart callback point and close it in this callback point.

You can also use this together with ApplicationServiceStart, HandlingRequestStart and HandlingRequestEnd to introduce a logging system for the application.

Abstract callback function

Inherit from Callback.WebServer.ApplicationServiceEnd.AbstractCallbackFunction to create a callback function that can be called by this callback point.