[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: primed pump [was: [soa-rm] conflict with today's meeting]
Thanks, Martin. - Unfortunately, the overused and under-defined term is coarse-grained interface. I’m happy to entertain alternate terms and better corresponding definitions. That’s part of what I was taking on here. - I’m not sure if there is something specific that needs rewording or an overall impression that I may have unintentionally created. A coarse-grained interface is more flexible in that it exposes widely used functionality without restricting use to a single use of that function. The example was GET as supporting a general retrieval function and not have it specialized to a single resource type. My separate point was that the idea of fine or coarse-grained service is somewhat subject to the consumer’s perspective. A service that is a composite of other services may not expose the component services but only the composite. This is neither good nor bad — it just is :) I think the composite would often (usually?) be considered coarser-grained. Is that a useful description? I’m not sure but it was part of what I was trying to straighten out. Keep those cards and letters coming, folks. Ken ------------------------------------------------------------------------------
Dr. Kenneth Laskey MITRE Corporation, M/S F510 phone: 703-983-7934 7515 Colshire Drive fax: 703-983-1379 McLean VA 22102-7508
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]