There are a plethora of services available that....
ae_component
A service used by remote and templating that
initializes the AE component facilities. This service, coupled with
the web, requestHandler and templating
services is what really makes the server tick.
aecgi
The service that handles the SkunkWeb server side of the
Apache (or actually anything that speaks the aecgi protocol) to
SkunkWeb connectivity.
fcgiprot
The service that allows FastCGI connections to the
SkunkWeb server.
basicauth
Allows for doing HTTP basic authentication (see section 7.3, page ).
httpd
Makes it so SkunkWeb can handle HTTP requests directly,
without the use of Apache. Requires the web service.
mysql
Service to cache MySQL connections
(see section 6.4, page ).
oracle
Service to cache Oracle connections and stored procedure
definitions (see section 6.4, page ).
pars
Allows the packaging of stuff that would normally be found in
the docroot to be stored in parfile archives (see section 7.2, page ).
postgresql
Service to cache PostgreSQL connections
(see section 6.4, page ).
remote
Allows SkunkWeb to serve remote component requests
(see section 6.1, page ); requires the requestHandler
and ae_component services.
remote_client
Allows SkunkWeb to make remote component requests
(see section 6.1, page ); requires the templating service.
requestHandler
Adds a request handling framework, built on top
of by some of the other services.
sessionHandler
Handles the persistence of user session data in
a MySQL database, the local filesystem, or other user-defined data store;
requires the web service.
templating
Hooks together the web and ae_component
services, in addition to adding a few tags.
userdir
Make it so requests under the uri
/user/rest, will go to the directory
users_home/public_html/rest.
web
Service to manage web requests and setup the
CONNECTION object; requires the requestHandler service.
