Also included in the repair code is handwritten code to tie the skeleton into component functionality. There are various options for wrapping the component's interface to switch from custom graphics to X-Windowing System. The key difference between a bridge and a wrapper is that the repair code constituting a bridge is independent of any particular component. This last point emphasizes the idea that bridges are usually transient processes. The significance of both of these distinctions will be made clear in the discussion of mediators.
Bridges typically focus on a narrower range of interface translations than the wrappers do.
This is because bridges address specific assumptions. The more assumptions a bridge tries to address, the fewer components it will apply to. We wish to integrate these components so that the display component can be invoked on design documents. The scenario brings to mind the use of Unix filters, although this is not the only mechanism that can be used in this scenario. A Unix shell script can execute the bridge.