HTTP service

The HTTP service has these actors:

Service administrator

Issues warrants for site owners to use the HTTP service.

Site owner

Uses an HTTP warrant to first negotiate for the resources required by their back end(s). They can provide the HTTP service with a DNS warrant so it can update their host name to match the (possibly variable) IP address of their Web site. As a distinct process the HTTP site owner will also be a Webtrix site owner (see next) and they will feed WAR files into their Webtrix site. Finally they will give a Webtrix back end warrant to the HTTP service so that it can access those WARs and hence make their site available to the general public.

Back end

A back end such as Webtrix uses the HTTP service to bind the requested resources.

The HTTP service has uses for these netlets:

Managers

Just store the application state. Also update any DNS services as made accessible by a site owner providing a DNS warrant.

Workers

Are the actual HTTP servers. The workers in any one worker pool all have the same kinds of resource available to them. When the HTTP service is given a new back end a manager will look for a worker pool with the right resources, or else will start a new one. Then the worker will bind the back end service. Incoming HTTP requests will get routed to the appropriate back end.

Access points

Just the default proxy access points.