Steve Jones wrote: > 2009/1/30 Rob Eamon <[email protected] <mailto:reamon%40cableone.net>>: > > In other words, I think it is better to think of "batch interface" > > rather than "batch service." The focus of the service is defining > > what "submit customer" does and then providing the interfaces needed > > by consumers, batch or otherwise. > > See above though, the characteristics of submit customer in a batch > are liable to be different, certainly from an SLA perspective (so its > at least interface + policy) and arguably from a behaviour perspective > (in the case of batch integrity).
This seems like a transactional behavior semantic. Wouldn't it work to just put a transactional mechanism on the service interface so that the whole batch could be run under a single transaction which would then be aborted if one item was not valid? Gregg Wonderly
