Engineering:Tie (information technology)
Please use PROD only on articles. It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Engineering:Tie (information technology)|concern=The coverage (references, external links, etc.) does not seem sufficient to justify this article passing Wikipedia:General notability guideline and the more detailed Wikipedia:Notability (software) requirement. If you disagree and deprod this, please explain how it meets them on the talk page here in the form of "This article meets criteria A and B because..." and ping me back through WP:ECHO or by leaving a note at User talk:Piotrus. Thank you.}} ~~~~Timestamp: 20181022103815 10:38, 22 October 2018 (UTC) Administrators: delete |
A tie is a concept to bind a class skeleton to an implementing class.
With this approach the class which should be invoked by a remote call, can be derived from a non-remoting class.
Usually a tie class is used in middleware systems, to perform delegation from the skeleton to an implementing class.
Example
Usually:
Stub -remote-> Skeleton (perform logic)
Tie Approach:
Stub -remote-> Tie Skeleton -delegate-> Class (perform logic)
References
 |
