Hi Tobias, All,
  On the one hand this is a 200 because our task is completed but on the
other hand its a 200 because the "redirection" to the resultURI referes
to an AMBIT task which is not yet completed at the time of 200. However
our task is completed so in my opinion this should be 200 for every
server that completes execution. BTW, I think the previous version of
the API was much more RESTful...but I think we can proceed with that :)

Best regards,
Pantelis

On Tue, 2010-04-27 at 11:24 +0200, Tobias Girschick wrote:
> Hi All,
> 
> On Tue, 2010-04-27 at 11:52 +0300, Nina Jeliazkova wrote: 
> > Hello Tobias,
> > 
> > Tobias Girschick wrote:
> > > Hello All,
> > >
> > > we removed the redirect from the TUM task services as suggested by
> > > Martin. All Tasks now return the resulting URI and status code 200 on
> > > finishing. No automatic redirects anymore. 
> > >   
> > Just to clarify - if a model completes execution and posts the result
> > dataset to the dataset service, what will be returned - 200 or 202 ?
> 
> Now I return 200. How are other groups handling this, e.g. Pantelis?
> Martin? 
> Nina told me that returning 200 will cause Problems with ToxPredict (at
> the moment). What exactly is expected by the validation services?
> 
> We definitely need a uniform solution here. What do other developers
> think? I have no problem returning 202 on completion (calculation
> completion) if the complete job is still not done (e.g. AMBIT upload
> initiated by my service). 
> 
> regards,
> Tobias
> 
> > 
> > Best regards,
> > Nina
> > > @Martin: Could you check if everything works fine now with the
> > > validation services?
> > >
> > > regards, 
> > > Tobias + Fabian
> > >
> > >   
> > 
> 
>