Show simple item record

Files in this item

Thumbnail

Item metadata

dc.contributor.authorDearle, Alan
dc.contributor.authorWalker, Scott
dc.contributor.authorNorcross, Stuart
dc.contributor.authorKirby, Graham
dc.contributor.authorMcCarthy, Andrew
dc.date.accessioned2011-03-30T15:31:32Z
dc.date.available2011-03-30T15:31:32Z
dc.date.issued2005
dc.identifier.citationDearle , A , Walker , S , Norcross , S , Kirby , G & McCarthy , A 2005 , RAFDA : Middleware supporting the separation of application logic from distribution policy . Technical Report , no. CS/05/3 , University of St Andrews .en
dc.identifier.otherPURE: 5009079
dc.identifier.otherPURE UUID: d9fed3e8-0081-4612-bdb9-00ca4d532b0e
dc.identifier.otherArXiv: http://arxiv.org/abs/1006.3742v1
dc.identifier.otherORCID: /0000-0002-4422-0190/work/28429109
dc.identifier.urihttps://hdl.handle.net/10023/1737
dc.descriptionSubmitted to Middleware 2005en
dc.description.abstractMiddleware technologies often limit the way in which object classes may be used in distributed applications due to the fixed distribution policies imposed by the Middleware system. These policies permeate the applications developed using them and force an unnatural encoding of application level semantics. For example, the application programmer has no direct control over inter-address-space parameter passing semantics since it is fixed by the application's distribution topology which is dictated early in the design cycle by the Middleware. This creates applications that are brittle with respect to changes in the way in which the applications are distributed. This paper explores technology permitting arbitrary objects in an application to be dynamically exposed for remote access. Using this, the application can be written without concern for its distribution with object placement and distribution boundaries decided late in the design cycle and even dynamically. Inter-address-space parameter passing semantics may also be decided independently of object implementation and at varying times in the design cycle, again, possibly as late as run-time. Furthermore, transmission policy may be defined on a per-class, per-method or per-parameter basis maximizing plasticity. This flexibility is of utility in the development of new distributed applications and the creation of management and monitoring infrastructures for existing applications.
dc.format.extent20
dc.language.isoeng
dc.publisherUniversity of St Andrews
dc.relation.ispartofseriesTechnical Reporten
dc.subjectcs.DCen
dc.subjectDistributed, parallel, and cluster computingen
dc.subjectQA75 Electronic computers. Computer scienceen
dc.subject.lccQA75en
dc.titleRAFDA : Middleware supporting the separation of application logic from distribution policyen
dc.typeReporten
dc.description.versionPreprinten
dc.contributor.institutionUniversity of St Andrews. School of Computer Scienceen
dc.identifier.urlhttp://arxiv.org/abs/1006.3742en


This item appears in the following Collection(s)

Show simple item record