On Fri, 24 May 2013, John MacAuley wrote:
What is the aggregator supposed to fill in ConnectionStatesType, when sending up notification, such as ErrorEvent? If it gets a single error event, the connection the aggregator represents won't be in a consistent state. There is a similar case with ReservationTimeout. Right now I have a set of state machines in the aggregator, but I am thinking that an RSM might not make an awful lot of sense in there at all.
The aggregator sends up the view of its connection states.
But the view of the aggregator is inconsistent.
This will let the parent know what, if any, transitions the aggregator went through as a result of the error.
Does this mean that it is stuck an in -ing state, or does it move back into previous states or into a failed state? Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet