IVOA Grid & Web Services: Asynchronous servicesContentsOverviewServices are defined as being asynchronous when an operation on a web service starts some activity and returns immediately, leaving the activity running remotely. This asychronicity is useful in making a robust VO and is already used in some VO prototypes, e.g. Astrogrid's Common Execution Architecture (CEA). A conceptual proposal for managing the activities was drawn up and presented to IVOA in 2004. This was formalized into the Universal Worker Service (UWS) pattern.Universal Worker ServiceUWS proposes that a minimal interface supports job creation, polling of job status and retrieval. A fuller interface would also allowing requesting an estimate of the duration of a job amd restarting a failed job from its last checkpoint. UWS-PA is an instantiation of the UWS pattern for parameterized applications (PA), i.e. applications whose input and output arguments can be expressed as a set of key-value pairs. CEA is an implementation of UWS-PA.SpecificationThe latest version of the UWS proposal is v1.0 and is currently a recommendation. Note from version 0.5 the source of the document is stored in the Volute GoogleCode Project
Discussion
HistoryThese are older versions of the UWS specification: | |||||||||
Changed: | |||||||||
< < | |||||||||
> > | |||||||||
Background reading
|
IVOA Grid & Web Services: Asynchronous servicesContentsOverviewServices are defined as being asynchronous when an operation on a web service starts some activity and returns immediately, leaving the activity running remotely. This asychronicity is useful in making a robust VO and is already used in some VO prototypes, e.g. Astrogrid's Common Execution Architecture (CEA). A conceptual proposal for managing the activities was drawn up and presented to IVOA in 2004. This was formalized into the Universal Worker Service (UWS) pattern.Universal Worker ServiceUWS proposes that a minimal interface supports job creation, polling of job status and retrieval. A fuller interface would also allowing requesting an estimate of the duration of a job amd restarting a failed job from its last checkpoint. UWS-PA is an instantiation of the UWS pattern for parameterized applications (PA), i.e. applications whose input and output arguments can be expressed as a set of key-value pairs. CEA is an implementation of UWS-PA.Specification | |||||||||
Changed: | |||||||||
< < | The latest version of the UWS proposal is v1.0 and is currently in RFC | ||||||||
> > | The latest version of the UWS proposal is v1.0 and is currently a recommendation. | ||||||||
Note from version 0.5 the source of the document is stored in the Volute GoogleCode Project
Discussion | |||||||||
Changed: | |||||||||
< < | |||||||||
> > |
| ||||||||
HistoryThese are older versions of the UWS specification:Background reading<--
|
IVOA Grid & Web Services: Asynchronous servicesContentsOverviewServices are defined as being asynchronous when an operation on a web service starts some activity and returns immediately, leaving the activity running remotely. This asychronicity is useful in making a robust VO and is already used in some VO prototypes, e.g. Astrogrid's Common Execution Architecture (CEA). A conceptual proposal for managing the activities was drawn up and presented to IVOA in 2004. This was formalized into the Universal Worker Service (UWS) pattern.Universal Worker ServiceUWS proposes that a minimal interface supports job creation, polling of job status and retrieval. A fuller interface would also allowing requesting an estimate of the duration of a job amd restarting a failed job from its last checkpoint. UWS-PA is an instantiation of the UWS pattern for parameterized applications (PA), i.e. applications whose input and output arguments can be expressed as a set of key-value pairs. CEA is an implementation of UWS-PA.Specification | |||||||||
Changed: | |||||||||
< < | The latest version of the UWS proposal is v0.5. It introduces new objects into the REST binding, as detailed in the Lessons learned from 0.4 document: Note from version 0.5 the source of the document is stored in the Volute GoogleCode Project | ||||||||
> > | The latest version of the UWS proposal is v1.0 and is currently in RFC | ||||||||
Changed: | |||||||||
< < | |||||||||
> > | |||||||||
Added: | |||||||||
> > | Note from version 0.5 the source of the document is stored in the Volute GoogleCode Project | ||||||||
DiscussionHistoryThese are older versions of the UWS specification: | |||||||||
Added: | |||||||||
> > | |||||||||
Background reading<--
|
IVOA Grid & Web Services: Asynchronous servicesContentsOverviewServices are defined as being asynchronous when an operation on a web service starts some activity and returns immediately, leaving the activity running remotely. This asychronicity is useful in making a robust VO and is already used in some VO prototypes, e.g. Astrogrid's Common Execution Architecture (CEA). A conceptual proposal for managing the activities was drawn up and presented to IVOA in 2004. This was formalized into the Universal Worker Service (UWS) pattern.Universal Worker ServiceUWS proposes that a minimal interface supports job creation, polling of job status and retrieval. A fuller interface would also allowing requesting an estimate of the duration of a job amd restarting a failed job from its last checkpoint. UWS-PA is an instantiation of the UWS pattern for parameterized applications (PA), i.e. applications whose input and output arguments can be expressed as a set of key-value pairs. CEA is an implementation of UWS-PA.Specification | |||||||||
Changed: | |||||||||
< < | The latest version of the UWS proposal is v0.4. It introduces new objects into the REST binding, as detailed in the Lessons learned from 0.3 document: | ||||||||
> > | The latest version of the UWS proposal is v0.5. It introduces new objects into the REST binding, as detailed in the Lessons learned from 0.4 document: Note from version 0.5 the source of the document is stored in the Volute GoogleCode Project | ||||||||
DiscussionHistoryThese are older versions of the UWS specification:Background reading<--
|
IVOA Grid & Web Services: Asynchronous servicesContentsOverviewServices are defined as being asynchronous when an operation on a web service starts some activity and returns immediately, leaving the activity running remotely. This asychronicity is useful in making a robust VO and is already used in some VO prototypes, e.g. Astrogrid's Common Execution Architecture (CEA). A conceptual proposal for managing the activities was drawn up and presented to IVOA in 2004. This was formalized into the Universal Worker Service (UWS) pattern.Universal Worker ServiceUWS proposes that a minimal interface supports job creation, polling of job status and retrieval. A fuller interface would also allowing requesting an estimate of the duration of a job amd restarting a failed job from its last checkpoint. UWS-PA is an instantiation of the UWS pattern for parameterized applications (PA), i.e. applications whose input and output arguments can be expressed as a set of key-value pairs. CEA is an implementation of UWS-PA.SpecificationThe latest version of the UWS proposal is v0.4. It introduces new objects into the REST binding, as detailed in the Lessons learned from 0.3 document:
DiscussionHistoryThese are older versions of the UWS specification:Background reading<--
| |||||||||
Changed: | |||||||||
< < |
| ||||||||
> > |
| ||||||||
IVOA Grid & Web Services: Asynchronous servicesContentsOverviewServices are defined as being asynchronous when an operation on a web service starts some activity and returns immediately, leaving the activity running remotely. This asychronicity is useful in making a robust VO and is already used in some VO prototypes, e.g. Astrogrid's Common Execution Architecture (CEA). A conceptual proposal for managing the activities was drawn up and presented to IVOA in 2004. This was formalized into the Universal Worker Service (UWS) pattern.Universal Worker ServiceUWS proposes that a minimal interface supports job creation, polling of job status and retrieval. A fuller interface would also allowing requesting an estimate of the duration of a job amd restarting a failed job from its last checkpoint. UWS-PA is an instantiation of the UWS pattern for parameterized applications (PA), i.e. applications whose input and output arguments can be expressed as a set of key-value pairs. CEA is an implementation of UWS-PA.SpecificationThe latest version of the UWS proposal is v0.4. It introduces new objects into the REST binding, as detailed in the Lessons learned from 0.3 document: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
DiscussionHistoryThese are older versions of the UWS specification: | ||||||||
Added: | ||||||||
> > | ||||||||
Background reading<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
IVOA Grid & Web Services: Asynchronous servicesContentsOverviewServices are defined as being asynchronous when an operation on a web service starts some activity and returns immediately, leaving the activity running remotely. This asychronicity is useful in making a robust VO and is already used in some VO prototypes, e.g. Astrogrid's Common Execution Architecture (CEA). A conceptual proposal for managing the activities was drawn up and presented to IVOA in 2004. This was formalized into the Universal Worker Service (UWS) pattern.Universal Worker ServiceUWS proposes that a minimal interface supports job creation, polling of job status and retrieval. A fuller interface would also allowing requesting an estimate of the duration of a job amd restarting a failed job from its last checkpoint. UWS-PA is an instantiation of the UWS pattern for parameterized applications (PA), i.e. applications whose input and output arguments can be expressed as a set of key-value pairs. CEA is an implementation of UWS-PA.Specification | ||||||||
Changed: | ||||||||
< < | The latest version of the UWS proposal is v0.3. It introduces a REST binding as an alternative to SOAP: | |||||||
> > | The latest version of the UWS proposal is v0.4. It introduces new objects into the REST binding, as detailed in the Lessons learned from 0.3 document: | |||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
DiscussionHistoryThese are older versions of the UWS specification: | ||||||||
Added: | ||||||||
> > | ||||||||
Background reading<--
| ||||||||
Added: | ||||||||
> > | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
IVOA Grid & Web Services: Asynchronous servicesContentsOverviewServices are defined as being asynchronous when an operation on a web service starts some activity and returns immediately, leaving the activity running remotely. This asychronicity is useful in making a robust VO and is already used in some VO prototypes, e.g. Astrogrid's Common Execution Architecture (CEA). A conceptual proposal for managing the activities was drawn up and presented to IVOA in 2004. This was formalized into the Universal Worker Service (UWS) pattern.Universal Worker ServiceUWS proposes that a minimal interface supports job creation, polling of job status and retrieval. A fuller interface would also allowing requesting an estimate of the duration of a job amd restarting a failed job from its last checkpoint. UWS-PA is an instantiation of the UWS pattern for parameterized applications (PA), i.e. applications whose input and output arguments can be expressed as a set of key-value pairs. CEA is an implementation of UWS-PA.SpecificationThe latest version of the UWS proposal is v0.3. It introduces a REST binding as an alternative to SOAP: | ||||||||
Added: | ||||||||
> > |
| |||||||
DiscussionHistoryThese are older versions of the UWS specification:Background reading<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
IVOA Grid & Web Services: Asynchronous servicesContentsOverviewServices are defined as being asynchronous when an operation on a web service starts some activity and returns immediately, leaving the activity running remotely. This asychronicity is useful in making a robust VO and is already used in some VO prototypes, e.g. Astrogrid's Common Execution Architecture (CEA). A conceptual proposal for managing the activities was drawn up and presented to IVOA in 2004. This was formalized into the Universal Worker Service (UWS) pattern.Universal Worker ServiceUWS proposes that a minimal interface supports job creation, polling of job status and retrieval. A fuller interface would also allowing requesting an estimate of the duration of a job amd restarting a failed job from its last checkpoint. UWS-PA is an instantiation of the UWS pattern for parameterized applications (PA), i.e. applications whose input and output arguments can be expressed as a set of key-value pairs. CEA is an implementation of UWS-PA.SpecificationThe latest version of the UWS proposal is v0.3. It introduces a REST binding as an alternative to SOAP: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
DiscussionHistoryThese are older versions of the UWS specification: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Background reading<--
|
IVOA Grid & Web Services: Asynchronous servicesContentsOverviewServices are defined as being asynchronous when an operation on a web service starts some activity and returns immediately, leaving the activity running remotely. This asychronicity is useful in making a robust VO and is already used in some VO prototypes, e.g. Astrogrid's Common Execution Architecture (CEA). A conceptual proposal for managing the activities was drawn up and presented to IVOA in 2004. This was formalized into the Universal Worker Service (UWS) pattern.Universal Worker ServiceUWS proposes that a minimal interface supports job creation, polling of job status and retrieval. A fuller interface would also allowing requesting an estimate of the duration of a job amd restarting a failed job from its last checkpoint. UWS-PA is an instantiation of the UWS pattern for parameterized applications (PA), i.e. applications whose input and output arguments can be expressed as a set of key-value pairs. CEA is an implementation of UWS-PA.Specification | ||||||||
Changed: | ||||||||
< < | The latest version of the UWS propasal is v0.3. It introduces a REST binding as an alternative to SOAP: | |||||||
> > | The latest version of the UWS proposal is v0.3. It introduces a REST binding as an alternative to SOAP: | |||||||
Discussion | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
History | ||||||||
Changed: | ||||||||
< < | These are older version of the UWS specification: | |||||||
> > | These are older versions of the UWS specification: | |||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Background reading<--
|
IVOA Grid & Web Services: Asynchronous servicesContentsOverviewServices are defined as being asynchronous when an operation on a web service starts some activity and returns immediately, leaving the activity running remotely. This asychronicity is useful in making a robust VO and is already used in some VO prototypes, e.g. Astrogrid's Common Execution Architecture (CEA). A conceptual proposal for managing the activities was drawn up and presented to IVOA in 2004. This was formalized into the Universal Worker Service (UWS) pattern.Universal Worker ServiceUWS proposes that a minimal interface supports job creation, polling of job status and retrieval. A fuller interface would also allowing requesting an estimate of the duration of a job amd restarting a failed job from its last checkpoint. UWS-PA is an instantiation of the UWS pattern for parameterized applications (PA), i.e. applications whose input and output arguments can be expressed as a set of key-value pairs. CEA is an implementation of UWS-PA.SpecificationThe latest version of the UWS propasal is v0.3. It introduces a REST binding as an alternative to SOAP:DiscussionHistoryThese are older version of the UWS specification:Background reading<--
|