• Treffer 7 von 25
Zurück zur Trefferliste

Malleability, obliviousness and aspects for broadcast service attachment

  • An important characteristic of Service-Oriented Architectures is that clients do not depend on the service implementation's internal assignment of methods to objects. It is perhaps the most important technical characteristic that differentiates them from more common object-oriented solutions. This characteristic makes clients and services malleable, allowing them to be rearranged at run-time as circumstances change. That improvement in malleability is impaired by requiring clients to direct service requests to particular services. Ideally, the clients are totally oblivious to the service structure, as they are to aspect structure in aspect-oriented software. Removing knowledge of a method implementation's location, whether in object or service, requires re-defining the boundary line between programming language and middleware, making clearer specification of dependence on protocols, and bringing the transaction-like concept of failure scopes into language semantics as well. This paper explores consequences and advantages of aAn important characteristic of Service-Oriented Architectures is that clients do not depend on the service implementation's internal assignment of methods to objects. It is perhaps the most important technical characteristic that differentiates them from more common object-oriented solutions. This characteristic makes clients and services malleable, allowing them to be rearranged at run-time as circumstances change. That improvement in malleability is impaired by requiring clients to direct service requests to particular services. Ideally, the clients are totally oblivious to the service structure, as they are to aspect structure in aspect-oriented software. Removing knowledge of a method implementation's location, whether in object or service, requires re-defining the boundary line between programming language and middleware, making clearer specification of dependence on protocols, and bringing the transaction-like concept of failure scopes into language semantics as well. This paper explores consequences and advantages of a transition from object-request brokering to service-request brokering, including the potential to improve our ability to write more parallel software.zeige mehrzeige weniger

Volltext Dateien herunterladen

Metadaten exportieren

Weitere Dienste

Suche bei Google Scholar Statistik - Anzahl der Zugriffe auf das Dokument
Metadaten
Verfasserangaben:William Harrison
URN:urn:nbn:de:kobv:517-opus-41389
Publikationstyp:Konferenzveröffentlichung
Sprache:Englisch
Erscheinungsjahr:2010
Veröffentlichende Institution:Universität Potsdam
Datum der Freischaltung:26.02.2010
Freies Schlagwort / Tag:aspect-oriented; concurrency; middleware; programming language; service-oriented
Quelle:Proceedings of the 9th Workshop on Aspects, Components, and Patterns for Infrastructure Software (ACP4IS '10) / Bram Adams, Michael Haupt, Daniel Lohmann (Hrsg.). - Potsdam : Universitätsverlag Potsdam, 2010. - ISBN 978-3-86956-043-4. - S. 41 - 47
Organisationseinheiten:An-Institute / Hasso-Plattner-Institut für Digital Engineering gGmbH
CCS-Klassifikation:D. Software / D.2 SOFTWARE ENGINEERING (K.6.3) / D.2.11 Software Architectures (NEW)
D. Software / D.3 PROGRAMMING LANGUAGES / D.3.3 Language Constructs and Features (E.2)
DDC-Klassifikation:0 Informatik, Informationswissenschaft, allgemeine Werke / 00 Informatik, Wissen, Systeme / 004 Datenverarbeitung; Informatik
Sammlung(en):Universität Potsdam / Tagungsbände/Proceedings (nicht fortlaufend) / Proceedings of the 9th Workshop on Aspects, Components, and Patterns for Infrastructure Software (ACP4IS \'10) / Session 3: Fantastic Frameworks and Infamous Infrastructures
Lizenz (Deutsch):License LogoKeine öffentliche Lizenz: Unter Urheberrechtsschutz
Verstanden ✔
Diese Webseite verwendet technisch erforderliche Session-Cookies. Durch die weitere Nutzung der Webseite stimmen Sie diesem zu. Unsere Datenschutzerklärung finden Sie hier.