Specification

f(x1...xn, y1...yn, ...) -> f(X)

Description

A special case of the mapper pattern, the bridge pattern can be used to map transport generated requests to NetKernel hosted services.

A transport initiated request will often provide a set of information associated with the event which occurred within the transport. In general this information is dispersed in transport dependent data structures. It is very valuable to route the request to a bridge service which will collect the dispersed information and reissue a sub-request for the required service with cleanly structured NetKernel active URI arguments containing the collected transport information.

Generally a bridge will take a declarative mapping definition which will describe what information should be collected and/or processed and how that should be constructed into the sub-request.

Usage

This pattern is extensively used in applications using the HTTP transport.