Mornin! After looking at the state model with a colleague (Victor), it was brought up that there are no exception states captured. Might it be appropriate to insert an error state such as “ERROR” or “CRASHED”? The assumption of the state model currently is that no failures occur but we should design with this in mind. Now perhaps failure is mitigated by provider internal strategies in which case exceptions are not revealed to a client but if a provider does not have advanced recovery strategies there’s no way to signal exceptions to a client (we should cater for lowest common denominator). Andy From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of Sam Johnston Sent: 20 April 2009 09:20 To: Thijs Metsch Cc: occi-wg@ogf.org Subject: Re: [occi-wg] OCCI MC - State Machine Diagram On Mon, Apr 20, 2009 at 9:57 AM, Thijs Metsch <Thijs.Metsch@sun.com<mailto:Thijs.Metsch@sun.com>> wrote: Ah sorry, my fault - than it was only that the picture was not updated...Was missing the entry-points :-) Finally worked out how to remove/update attachments. Done. Sam ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.