Middleware (distributed applications): Difference between revisions

Revision as of 12:54, 22 June 2018

Revision as of 07:27, 20 October 2018

Line 62:

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 }}, 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.

; Remote procedure callcal

: [[Remote procedure call]] middleware enables a client to use services running on remote systems. The process can be [[Synchronization (computer science)|synchronous]] or [[Asynchrony (computer programming)|asynchronous]].

; Object request broker