Transport Matching PatternTransport Matching Pattern
The Transport/Protocol Matching Design Pattern
Home > Books > Architect's Guide to NetKernel > Design Patterns > Transport Matching Pattern

Rate this page:
Really useful
Satisfactory
Not helpful
Confusing
Incorrect
Unsure
Extra comments:


Specification

t1(j)->m1(j) -> f(x)

t2(k)->m2(k) -> f(x)

Description

The transport (or protocol) matching pattern enables a single internal service implementation to be simultaneously exposed over a number of external transports (or application protocols) by introducing an impedance matching mapper service between each transport and the implementing service.

Usage

This pattern is very valuable for simultaneously exposing a single service as both SOAP and REST web-services and even allows for presenting the same service with XHTML form-based and/or email interfaces.

© 2003-2007, 1060 Research Limited. 1060 registered trademark, NetKernel trademark of 1060 Research Limited.