Synchrony abstraction
This article may meet Wikipedia's criteria for speedy deletion as a copyright infringement(Copyvios report) of http://elemenope.org/doc/userguide/userguide-1.0.pdf (Copyvios report). This criterion applies only in unequivocal cases, where there is no free-content material on the page worth saving and no later edits requiring attribution – for more complicated situations, see Wikipedia:Copyright violations. See CSD G12.
If this article does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with the given reason for deletion, you can click the button below and leave a message explaining why you believe it should not be deleted. You can also visit the talk page to check if you have received a response to your message. Note that this article may be deleted at any time if it unquestionably meets the speedy deletion criteria, or if an explanation posted to the talk page is found to be insufficient.
Note to administrators: this article has content on its talk page which should be checked before deletion. Note to administrators: If declining the request due to not meeting the criteria please consider whether there are still copyright problems with the page and if so, see these instructions for cleanup, or list it at Wikipedia:Copyright problems. Please be sure that the source of the alleged copyright violation is not itself a Wikipedia mirror. Also, ensure the submitter of this page has been notified about our copyright policy.Administrators: check links, talk, history (last), and logs before deletion. Consider checking Google. This page was last edited by Fossjunkie (contribs | logs) at 03:39, 29 May 2007 (UTC) (17 years ago) |
Abstraction of Synchrony is the proposed ability to generically call a Service/Operation without regard to whether the target service is configured as a Synchronous or Asynchronous protocol. The user may then call all services and expect a reply which may be utilized generically.
This architectural abstraction is made necessary due to Functional logic (business logic) abstraction, which is the capability of separating business logic implementation code from the service protocol implementation calling it. The fact that business logic implementations (operations) may be implemented in Synchronous or Asynchronous manners and that these business logic implementations may be interchangeable can cause problems when not addressed.
Source
elemenope User Guide