Show simple item record

Files in this item

Thumbnail

Item metadata

dc.contributor.advisorDearle, Alan
dc.contributor.advisorKirby, Graham N. C.
dc.contributor.authorWalker, Scott Mervyn
dc.coverage.spatialviii, 220 p.en
dc.date.accessioned2007-01-16T19:28:17Z
dc.date.available2007-01-16T19:28:17Z
dc.date.issued2006
dc.identifieruk.bl.ethos.551956
dc.identifier.urihttps://hdl.handle.net/10023/154
dc.description.abstractMiddleware augments operating systems and network infrastructure to assist in the creation of distributed applications in a heterogeneous environment. Current middleware systems exhibit some or all of the following five main problems: 1. Decisions must be made early in the design process. 2. Applications are inflexible to dynamic changes in their distribution. 3. Application development is complex and error-prone. 4. Existing systems force an unnatural encoding of application-level semantics. 5. Approaches to the specification of distribution policy are limited. This thesis defines a taxonomy of existing middleware systems and describes their limitations. The requirements that must be met by a third generation middleware system are defined and implemented by a system called the RAFDA Run-Time (RRT). The RRT allows control over the extent to which inter-address-space communication is exposed to programmers, aiding the creation, maintenance and evolution of distributed applications. The RRT permits the introduction of distribution into applications quickly and with minimal programmer effort, allowing for quick application prototyping. Programmers can conceal or expose the distributed nature of applications as required. The RRT allows instances of arbitrary application classes to be exposed to remote access as Web Services, provides control over the parameter-passing semantics applied to remote method calls and permits the creation of flexible distribution policies. The design of the RRT is described and evaluated qualitatively in the context of a case study based around the implementation of a peer-to-peer overlay network. A prototype implementation of the RRT is examined and evaluated quantitatively. Programmers determine the trade off between flexibility and simplicity offered by the RRT on a per-application basis, by concealing or exposing inter-address-space communication. The RRT is a middleware system that adapts to the needs of applications, rather than forcing distributed applications to adapt to the needs of the middleware system.en
dc.format.extent1404989 bytes
dc.format.mimetypeapplication/pdf
dc.language.isoenen
dc.publisherUniversity of St Andrews
dc.rightsCreative Commons Attribution-NonCommercial-NoDerivs 2.5 Generic
dc.rights.urihttp://creativecommons.org/licenses/by-nc-nd/2.5/
dc.subjectMiddlewareen
dc.subjectReflectionen
dc.subject.lccQA76.76M54W2
dc.subject.lcshMiddlewareen
dc.subject.lcshElectronic data processing--Distributed processingen
dc.titleA flexible, policy-aware middleware systemen
dc.typeThesisen
dc.type.qualificationlevelDoctoralen
dc.type.qualificationnamePhD Doctor of Philosophyen
dc.publisher.institutionThe University of St Andrewsen


The following licence files are associated with this item:

  • Creative Commons

This item appears in the following Collection(s)

Show simple item record

Creative Commons Attribution-NonCommercial-NoDerivs 2.5 Generic
Except where otherwise noted within the work, this item's licence for re-use is described as Creative Commons Attribution-NonCommercial-NoDerivs 2.5 Generic