Teleinterface
From APIDesign
(Difference between revisions)
Line 5: | Line 5: | ||
Just like a [[wikipedia::teleport|teleport]] that allows to transfer people between two distinct locations in a hyperspace a [[Teleinterface]] transfers information between distant [[API]] parties without being spotted meanwhile. | Just like a [[wikipedia::teleport|teleport]] that allows to transfer people between two distinct locations in a hyperspace a [[Teleinterface]] transfers information between distant [[API]] parties without being spotted meanwhile. | ||
- | [[Lookup]] is one possible way to realize a [[Teleinterface]]. [[MagicalStrings]] are other. | + | [[Lookup]] is one possible way to realize a [[Teleinterface]]. [[MagicalStrings]] are other. Both of these cases use some form of ''opaque container'' that flows through the [[API]], without being interpreted. |
[[Category:APIDesignPatterns]] | [[Category:APIDesignPatterns]] | ||
[[Category:APIDesignPatterns:Meta]] | [[Category:APIDesignPatterns:Meta]] |
Revision as of 10:06, 9 May 2010
Special meta-API Design Pattern that allows two parties to communicate via an interface that does not understand the whole complexity of the communication. Somehow the information flows from one side to another without being observed by the API itself.
Just like a teleport that allows to transfer people between two distinct locations in a hyperspace a Teleinterface transfers information between distant API parties without being spotted meanwhile.
Lookup is one possible way to realize a Teleinterface. MagicalStrings are other. Both of these cases use some form of opaque container that flows through the API, without being interpreted.