Content deleted Content added
Rescuing 2 sources and tagging 0 as dead. #IABot (v2.0beta10ehf1) |
Rescuing 4 sources and tagging 1 as dead. #IABot (v2.0beta10ehf1) |
||
Line 48:
===Message-oriented middleware===
[[Message-oriented middleware]] (MOM) <ref>Curry, Edward. 2004. [http://www.mendeley.com/download/public/1652511/4338215212/cce0f06f047faa57879a1fc36a8e8d6d754d2f6a/dl.pdf "Message-Oriented Middleware"]{{Dead link|date=January 2019 |bot=InternetArchiveBot |fix-attempted=yes }}<div id="zQYvwimRNZ" class="donut-container" style="cursor: pointer; display: inline-block; display: -webkit-inline-box; width: 16px; height: 16px;"><div data-reactroot="" class="donut donut_green"></div></div>{{dead link|date=June 2017 |bot=InternetArchiveBot |fix-attempted=yes }}. In Middleware for Communications, ed. Qusay H Mahmoud, 1-28. Chichester, England: John Wiley and Sons. {{doi|10.1002/0470862084.ch1}}<div id="hK_yD_rRqW" class="donut-container" style="cursor: pointer; display: inline-block; display: -webkit-inline-box; width: 16px; height: 16px;"><div data-reactroot="" class="donut donut_green"></div></div>. {{ISBN|978-0-470-86206-3}}</ref> is middleware where transactions or event notifications are delivered between disparate systems or components by way of messages, often via an [[enterprise messaging system]]. With MOM, messages sent to the client are collected and stored until they are acted upon, while the client continues with other processing.
; Enterprise messaging
Line 57:
===Intelligent middleware===
<ref>"[http://www.cougaarsoftware.com/files/CSI_ActiveEdge.pdf Choosing the Right Middleware] {{Webarchive|url=https://web.archive.org/web/20120402121113/http://www.cougaarsoftware.com/files/CSI_ActiveEdge.pdf |date=2012-04-02 }}<div id="GVZYiUdlia" class="donut-container" style="cursor: pointer; display: inline-block; display: -webkit-inline-box; width: 16px; height: 16px;"><div data-reactroot="" class="donut donut_gray"></div></div> {{
[[Category:Webarchive template wayback links]]
"</ref>
Line 63:
==={{Anchor|EMBEDDED}}Content-centric middleware===
Content-centric middleware offers a simple ''provider-consumer'' abstraction through which applications can issue requests for uniquely identified content, without worrying about where or how it is obtained. Juno is one example, which allows applications to generate content requests associated with high-level delivery requirements.<ref>[http://www.dcs.kcl.ac.uk/staff/tysong/files/PhD.pdf Juno] {{Webarchive|url=https://web.archive.org/web/20110426045143/http://www.dcs.kcl.ac.uk/staff/tysong/files/PhD.pdf |date=2011-04-26 }}<div id="uzEaKVwSoh" class="donut-container" style="cursor: pointer; display: inline-block; display: -webkit-inline-box; width: 16px; height: 16px;"><div data-reactroot="" class="donut donut_green"></div></div> {{
[[Category:Webarchive template wayback links]]
, Gareth Tyson, A Middleware Approach to Building Content-Centric Applications. PhD Thesis, Lancaster University (2010).</ref> The middleware then adapts the underlying delivery to access the content from sources that are best suited to matching the requirements. This is therefore similar to [[Publish/subscribe]] middleware, as well as the [[Content-centric networking]] paradigm.
| |||