Pipelines

Simple request processing pipeline is described at wiki Home page, this sample describes pipeline for complex application with standart UI and API services.

As in the simple example, every pipeline should start with root ExceptionRequestHandler. Here we can define application global error pages. This handler should work as backup for other exception handlers, more specific to the HTTP request structures.

Under root handler, there should by RoutingRequestHandler with three handler:

• First one for requests to static files (images, javascripts and stylesheets), prefixed with '/static-files' for example.
• Second one for requests to API, prefixed with '/api' for example.
• And third for requests to standart UI.

The first handler is quite obvious. The second one should be ExceptionRequestHandler with registered handlers and error message (XML or JSON or whatever) generators for processing exceptions. Under this handler, there should be another RoutingRequestHandler for dispatching API requests to, for example, WebStack.Services classes.

The third handler is for handling standart UI (html) requests. This one is also realized with RoutingRequestHandler and maps URLs for MVC like architecture or CMS based application.