[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [soa-rm] Groups - Rough notes taken during the last ebSOAmeeting. (ebSOA-Elements.pdf) uploaded
IMO a Service Oriented Architecture is more then *just* a service architecture. For example looking at a complex architecture where a provider has out-sourced their credit check functionality to another company, their shipping to a third company and their billing to a fourth company; the architecture of the interactions between all five companies are a legitimate concern of the reference model. These interactions may include such things as policy negotiation, etc. I agree that the structure and transport of the request/response should not be part of the reference model as this is an implementation issue. However, there are architectural features of the "message" interaction that should be included, as suggested above. Perhaps the term "message" should not be used in this instance as it has the connotation of a request/reply structure and transport. May I suggest Interaction Architecture. Don -- Don Flinn President, Flint Security LLC Tel: 781-856-7230 Fax: 781-631-7693 e-mail: flinn@alum.mit.edu http://flintsecurity.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]