Difference: AsynchronousHome (1 vs. 11)

Revision 112012-06-26 - root

 
META TOPICPARENT name="IvoaGridAndWebServices"

IVOA Grid & Web Services: Asynchronous services

Contents


Overview

Services 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 Service

UWS 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

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

History

These are older versions of the UWS specification:
Changed:
<
<
>
>
 


Background reading


META FILEATTACHMENT attr="" comment="Lessons Learned from implementing UWS 0.3" date="1210783524" name="ImplementingUWS-0.1.pdf" path="ImplementingUWS-0.1.pdf" size="155784" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4" date="1212743588" name="UWS-0.4.pdf" path="UWS-0.4.pdf" size="320971" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4 source document" date="1212743641" name="UWS-0.4.odt" path="UWS-0.4.odt" size="254821" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.5" date="1223476848" name="UWS-0.5.pdf" path="UWS-0.5.pdf" size="586344" user="PaulHarrison" version="1.2"

Revision 102011-04-12 - PaulHarrison

 
META TOPICPARENT name="IvoaGridAndWebServices"

IVOA Grid & Web Services: Asynchronous services

Contents


Overview

Services 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 Service

UWS 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:
<
<
>
>
 

History

These are older versions of the UWS specification:


Background reading


<--  
-->

META FILEATTACHMENT attr="" comment="Lessons Learned from implementing UWS 0.3" date="1210783524" name="ImplementingUWS-0.1.pdf" path="ImplementingUWS-0.1.pdf" size="155784" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4" date="1212743588" name="UWS-0.4.pdf" path="UWS-0.4.pdf" size="320971" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4 source document" date="1212743641" name="UWS-0.4.odt" path="UWS-0.4.odt" size="254821" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.5" date="1223476848" name="UWS-0.5.pdf" path="UWS-0.5.pdf" size="586344" user="PaulHarrison" version="1.2"

Revision 92009-10-05 - PaulHarrison

 
META TOPICPARENT name="IvoaGridAndWebServices"

IVOA Grid & Web Services: Asynchronous services

Contents


Overview

Services 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 Service

UWS 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
 

Discussion

History

These are older versions of the UWS specification:

Added:
>
>
 


Background reading


<--  
-->

META FILEATTACHMENT attr="" comment="Lessons Learned from implementing UWS 0.3" date="1210783524" name="ImplementingUWS-0.1.pdf" path="ImplementingUWS-0.1.pdf" size="155784" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4" date="1212743588" name="UWS-0.4.pdf" path="UWS-0.4.pdf" size="320971" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4 source document" date="1212743641" name="UWS-0.4.odt" path="UWS-0.4.odt" size="254821" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.5" date="1223476848" name="UWS-0.5.pdf" path="UWS-0.5.pdf" size="586344" user="PaulHarrison" version="1.2"

Revision 82009-04-29 - PaulHarrison

 
META TOPICPARENT name="IvoaGridAndWebServices"

IVOA Grid & Web Services: Asynchronous services

Contents


Overview

Services 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 Service

UWS 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
 

Discussion

History

These are older versions of the UWS specification:


Background reading


<--  
-->

META FILEATTACHMENT attr="" comment="Lessons Learned from implementing UWS 0.3" date="1210783524" name="ImplementingUWS-0.1.pdf" path="ImplementingUWS-0.1.pdf" size="155784" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4" date="1212743588" name="UWS-0.4.pdf" path="UWS-0.4.pdf" size="320971" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4 source document" date="1212743641" name="UWS-0.4.odt" path="UWS-0.4.odt" size="254821" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.5" date="1223476848" name="UWS-0.5.pdf" path="UWS-0.5.pdf" size="586344" user="PaulHarrison" version="1.2"

Revision 72008-10-08 - PaulHarrison

 
META TOPICPARENT name="IvoaGridAndWebServices"

IVOA Grid & Web Services: Asynchronous services

Contents


Overview

Services 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 Service

UWS 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

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:

Discussion

History

These are older versions of the UWS specification:


Background reading


<--  
-->

META FILEATTACHMENT attr="" comment="Lessons Learned from implementing UWS 0.3" date="1210783524" name="ImplementingUWS-0.1.pdf" path="ImplementingUWS-0.1.pdf" size="155784" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4" date="1212743588" name="UWS-0.4.pdf" path="UWS-0.4.pdf" size="320971" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4 source document" date="1212743641" name="UWS-0.4.odt" path="UWS-0.4.odt" size="254821" user="PaulHarrison" version="1.1"
Changed:
<
<
META FILEATTACHMENT attr="" comment="UWS 0.5" date="1223476063" name="UWS-0.5.pdf" path="UWS-0.5.pdf" size="586439" user="PaulHarrison" version="1.1"
>
>
META FILEATTACHMENT attr="" comment="UWS 0.5" date="1223476848" name="UWS-0.5.pdf" path="UWS-0.5.pdf" size="586344" user="PaulHarrison" version="1.2"
 

Revision 62008-10-08 - PaulHarrison

 
META TOPICPARENT name="IvoaGridAndWebServices"

IVOA Grid & Web Services: Asynchronous services

Contents


Overview

Services 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 Service

UWS 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

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:
<
<
>
>
 

Discussion

History

These are older versions of the UWS specification:

Added:
>
>
 


Background reading


<--  
-->

META FILEATTACHMENT attr="" comment="Lessons Learned from implementing UWS 0.3" date="1210783524" name="ImplementingUWS-0.1.pdf" path="ImplementingUWS-0.1.pdf" size="155784" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4" date="1212743588" name="UWS-0.4.pdf" path="UWS-0.4.pdf" size="320971" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4 source document" date="1212743641" name="UWS-0.4.odt" path="UWS-0.4.odt" size="254821" user="PaulHarrison" version="1.1"
Added:
>
>
META FILEATTACHMENT attr="" comment="UWS 0.5" date="1223476063" name="UWS-0.5.pdf" path="UWS-0.5.pdf" size="586439" user="PaulHarrison" version="1.1"
 

Revision 52008-06-06 - PaulHarrison

 
META TOPICPARENT name="IvoaGridAndWebServices"

IVOA Grid & Web Services: Asynchronous services

Contents


Overview

Services 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 Service

UWS 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:
<
<
>
>
 

Discussion

History

These are older versions of the UWS specification:

Added:
>
>
 


Background reading


<--  
-->
Added:
>
>
 
META FILEATTACHMENT attr="" comment="Lessons Learned from implementing UWS 0.3" date="1210783524" name="ImplementingUWS-0.1.pdf" path="ImplementingUWS-0.1.pdf" size="155784" user="PaulHarrison" version="1.1"
Added:
>
>
META FILEATTACHMENT attr="" comment="UWS 0.4" date="1212743588" name="UWS-0.4.pdf" path="UWS-0.4.pdf" size="320971" user="PaulHarrison" version="1.1"
META FILEATTACHMENT attr="" comment="UWS 0.4 source document" date="1212743641" name="UWS-0.4.odt" path="UWS-0.4.odt" size="254821" user="PaulHarrison" version="1.1"
 

Revision 42008-05-14 - PaulHarrison

 
META TOPICPARENT name="IvoaGridAndWebServices"

IVOA Grid & Web Services: Asynchronous services

Contents


Overview

Services 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 Service

UWS 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

The latest version of the UWS proposal is v0.3. It introduces a REST binding as an alternative to SOAP:

Added:
>
>
 

Discussion

History

These are older versions of the UWS specification:


Background reading


<--  
-->
Added:
>
>
META FILEATTACHMENT attr="" comment="Lessons Learned from implementing UWS 0.3" date="1210783524" name="ImplementingUWS-0.1.pdf" path="ImplementingUWS-0.1.pdf" size="155784" user="PaulHarrison" version="1.1"
 

Revision 32008-05-08 - MatthewGraham

 
META TOPICPARENT name="IvoaGridAndWebServices"

IVOA Grid & Web Services: Asynchronous services

Contents


Overview

Services 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 Service

UWS 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

The latest version of the UWS proposal is v0.3. It introduces a REST binding as an alternative to SOAP:
Changed:
<
<
>
>
 

Discussion

History

These are older versions of the UWS specification:
Changed:
<
<
>
>
 


Background reading


<--  
-->

Revision 22008-04-24 - MatthewGraham

 
META TOPICPARENT name="IvoaGridAndWebServices"

IVOA Grid & Web Services: Asynchronous services

Contents


Overview

Services 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 Service

UWS 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


<--  
-->

Revision 12008-04-24 - MatthewGraham

 
META TOPICPARENT name="IvoaGridAndWebServices"

IVOA Grid & Web Services: Asynchronous services

Contents


Overview

Services 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 Service

UWS 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

The latest version of the UWS propasal is v0.3. It introduces a REST binding as an alternative to SOAP:

Discussion

History

These are older version of the UWS specification:


Background reading


<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback