Re: [ogsa-hpcp-wg] Version 0.1 of HPC Basic Profile document
Marvin: Regarding: "The only restriction on the BES base case specification is that for the GetActivitiesStatus, TerminateActivities, and GetJSDLDocuments operations the length of the input vector of activities parameter MUST be exactly 1." Is there a need to indicate the error that should be returned if the length is different than 1? Ian. At 10:49 PM 8/24/2006 -0700, Marvin Theimer wrote:
Hi;
Enclosed is the revised version of the HPC Basic Profile document. I've added the paragraph to section 3 making it explicit that JSDL documents MAY include additional elements that a compliant system may respond to with a fault and I've filled in section 4 on BES.
Marvin.
_______________________________________________________________ Ian Foster -- Weblog: http://ianfoster.typepad.com Computation Institute: www.ci.uchicago.edu & www.ci.anl.gov Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 Tel: +1 630 252 4619 --- Globus Alliance: www.globus.org
Ian, all, without having the draft read yet: Inspired from the (obviously extremely successful *g*) HTTP/1.1 specification, I would apply "be generous in what you accept, but exact in what you emit" here: So I would suggest stating that a client SHOULD send vectors of length 1, and the consuming service SHOULD accept longer vectors. However, the service MUST consume only the first element in that input vector. That would relieve us from defining faults for this case (faults for empty or non-existing input vectors still apply, though). Cheers, Michel Ian Foster wrote:
Marvin:
Regarding: "The only restriction on the BES base case specification is that for the GetActivitiesStatus, TerminateActivities, and GetJSDLDocuments operations the length of the input vector of activities parameter MUST be exactly 1."
Is there a need to indicate the error that should be returned if the length is different than 1?
Ian.
At 10:49 PM 8/24/2006 -0700, Marvin Theimer wrote:
Hi;
Enclosed is the revised version of the HPC Basic Profile document. I've added the paragraph to section 3 making it explicit that JSDL documents MAY include additional elements that a compliant system may respond to with a fault and I've filled in section 4 on BES.
Marvin.
_______________________________________________________________ Ian Foster -- Weblog: http://ianfoster.typepad.com <http://ianfoster.typepad.com/> Computation Institute: www.ci.uchicago.edu <http://www.ci.uchicago.edu/> & www.ci.anl.gov <http://www.ci.anl.gov/> Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 Tel: +1 630 252 4619 --- Globus Alliance: www.globus.org <http://www.globus.org/>
-- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834
cool ... nice thinking -- Ian. At 08:43 AM 8/25/2006 +0100, Michel Drescher wrote:
Ian, all,
without having the draft read yet:
Inspired from the (obviously extremely successful *g*) HTTP/1.1 specification, I would apply "be generous in what you accept, but exact in what you emit" here:
So I would suggest stating that a client SHOULD send vectors of length 1, and the consuming service SHOULD accept longer vectors. However, the service MUST consume only the first element in that input vector.
That would relieve us from defining faults for this case (faults for empty or non-existing input vectors still apply, though).
Cheers, Michel
Ian Foster wrote:
Marvin: Regarding: "The only restriction on the BES base case specification is that for the GetActivitiesStatus, TerminateActivities, and GetJSDLDocuments operations the length of the input vector of activities parameter MUST be exactly 1." Is there a need to indicate the error that should be returned if the length is different than 1? Ian.
At 10:49 PM 8/24/2006 -0700, Marvin Theimer wrote:
Hi;
Enclosed is the revised version of the HPC Basic Profile document. I've added the paragraph to section 3 making it explicit that JSDL documents MAY include additional elements that a compliant system may respond to with a fault and I've filled in section 4 on BES.
Marvin.
Ian Foster -- Weblog: http://ianfoster.typepad.com <http://ianfoster.typepad.com/> Computation Institute: www.ci.uchicago.edu <http://www.ci.uchicago.edu/> & www.ci.anl.gov <http://www.ci.anl.gov/> Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 Tel: +1 630 252 4619 --- Globus Alliance: www.globus.org <http://www.globus.org/>
-- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834
_______________________________________________________________ Ian Foster -- Weblog: http://ianfoster.typepad.com Computation Institute: www.ci.uchicago.edu & www.ci.anl.gov Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 Tel: +1 630 252 4619 --- Globus Alliance: www.globus.org
participants (2)
-
Ian Foster -
Michel Drescher