Opposite of Facade?

[K]

Is there a design pattern that's the conceptual opposite of a facade?
While a facade presents a single interface to a more complex
underlying mechanism (fan out), is there a pattern that presents a
diverse range of interfaces to a single, simple underlying mechanism?

For example, I have a component that takes in XML data and transforms,
enriches and manipulates it. This is the single underlying component.
However, the component can receive this XML data from several
different sources and transports such as HTTP, JMS, etc. In effect,
this component is presenting multiple, diverse interfaces to the same
function.

Is there a design pattern that talks about this? If so what is it and
where can I find more information about it?

TIA

[H. S. Lahman]

Responding to K...

Post by K
Is there a design pattern that's the conceptual opposite of a facade?
While a facade presents a single interface to a more complex
underlying mechanism (fan out), is there a pattern that presents a
diverse range of interfaces to a single, simple underlying mechanism?
For example, I have a component that takes in XML data and transforms,
enriches and manipulates it. This is the single underlying component.
However, the component can receive this XML data from several
different sources and transports such as HTTP, JMS, etc. In effect,
this component is presenting multiple, diverse interfaces to the same
function.
Is there a design pattern that talks about this? If so what is it and
where can I find more information about it?

I don't think so. It is fundamental to OOA/D that interfaces are
separate from the objects they encapsulate and one can have multiple
interfaces to access the object. Modern OOPLs like Java explicitly
support this with language constructs. So one doesn't really need a
pattern; it is already part of the OOA/D notation or OOPL syntax.
--
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
***@pathfindermda.com
Pathfinder Solutions
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
"Model-Based Translation: The Next Step in Agile Development". Email
***@pathfindermda.com for your copy.
Pathfinder is hiring:
http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH