On Thu, Sep 19, 2013 at 03:26:46PM -0700, [email protected] wrote: > > (...) > > Due to the asynchronous nature of ruote, perhaps the web callback should > just return a 200 as long as the request was received and ruote was > successfully told to proceed to the next step. Then, we would use some > other mechanism to handle the case where ruote was unable to move to the > next step for some reason. Or, perhaps there's a better way to accomplish > what we're trying to do.
Hello, I would immediately respond with 200. Responding with 202 (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html) might be better, but you then would have to put your HTTP hat on and rethink your interactions. A service should do its job and not care about the result's further processing. Unless you want to stop orchestrating and let the services coordinate. Best regards, -- John Mettraux - http://lambda.io/jmettraux -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
