NOTE: The galeon mailing list is no longer active. The list archives are made available for historical reasons.
Dear Stefano, This looks good to me. My only comment is about the details of the asynchronous-interaction-with-storage case (the last case). The sequence diagram shows multiple GETs on the resourceURI. My understanding of WPS (which may be faulty) is that the first GET is on the resourceURI, which results in an ExecuteResponse document (as you say). The ER document contains a new URI which can be polled to get status information. Therefore it's my understanding that subsequent GETs will be on this new URI and will return an updated ER document (with status code 200 OK) until the document shows progress=complete. However, this might just be my interpretation, and I am not up to speed with WPS. Best wishes, Jon On Mon, Oct 20, 2008 at 3:22 PM, Stefano Nativi <nativi@xxxxxxxxxxx> wrote:
Steve and Aron, Some time ago, in the GALEON framework we discussed about a WCS RFC to: 1) Enable Grid Computing support of Access Services; 2) Support of long time processing; 3) Support redirection and "shared access". In order to support this request, we prepared a discussion paper: I attached the draft document hoping it could be useful for the present discussion. Best, Stefano
galeon archives: