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 a transitiAn 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.show moreshow less

Download full text files

Export metadata

  • Export Bibtex
  • Export RIS
  • Export XML

Additional Services

Share in Twitter Search Google Scholar
Metadaten
Author:William Harrison
URN:urn:nbn:de:kobv:517-opus-41389
Document Type:Conference Proceeding
Language:English
Date of Publication (online):2010/02/26
Year of Completion:2010
Publishing Institution:Universität Potsdam
Release Date:2010/02/26
Tag:aspect-oriented; concurrency; middleware; programming language; service-oriented
Source: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
Organizational units:An-Institute / Hasso-Plattner-Institut für Softwaresystemtechnik GMBH
CCS Classification: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)
Dewey Decimal Classification:0 Informatik, Informationswissenschaft, allgemeine Werke / 00 Informatik, Wissen, Systeme / 004 Datenverarbeitung; Informatik
Collections:Universität Potsdam / Tagungen / Proceedings of the 9th Workshop on Aspects, Components, and Patterns for Infrastructure Software (ACP4IS \'10) / Session 3: Fantastic Frameworks and Infamous Infrastructures
Licence (German):License LogoKeine Nutzungslizenz vergeben - es gilt das deutsche Urheberrecht