----- Original Message ----- > From: "Jan Provaznik" <[email protected]> > To: [email protected] > Sent: Wednesday, January 2, 2013 4:48:31 AM > Subject: Re: State Transitions in ReST API > > Hi, my late $0.2: > Conductor abstracts (should abstract) from any provider specific > state > transition differences, the state machine should be same in all > cases. > I think that just documenting state transitions in API doc would be > sufficient solution. > > With current Conductor capabilities, I can't think of any reasonable > use > case where a developer would choose processing state machine API. As > I > understood this API is required by Winged Monkey folks - could you > guys > please confirm that you want/need this API? > > Not sure if it's a blocker for you but implementing this feature > (state > machine + API) will take at least 2 sprints (optimistic estimation). > > Jan >
>From the Winged Monkey perspective, we can work with either solution, so I >think we'd prefer the one that gets it out the door the fastest :) Mainn
