... | ... | @@ -8,7 +8,8 @@ |
|
|
6. Interactive support to session directory (with proper protection and WebDAV basic support)
|
|
|
7. Machine readable error/result codes/messages
|
|
|
8. Re-use of existing software modules (no drastic changes to information representation and jobs handling)
|
|
|
9. ...
|
|
|
9. Bulk operations
|
|
|
10. ...
|
|
|
|
|
|
|
|
|
* Possible design.
|
... | ... | @@ -31,17 +32,19 @@ Delegation as resource |
|
|
|
|
|
Job control functionality:
|
|
|
<base URL>/jobs
|
|
|
- Initiate new job (POST, should PUT into subdir also create new job?)
|
|
|
- Initiate new job(s) (POST, should PUT into subdir also create new job?)
|
|
|
|
|
|
Job as resource. Each job is represented by URL
|
|
|
<base URL>/jobs/<job id>
|
|
|
- Modify job - cancel, pause, resume (POST, similar to new job creation?)
|
|
|
- Clean job (DELETE)
|
|
|
- Use <base URL>/jobs for bulk operations with additional parameters for specifying jobs? Or use HTTP 2.0 multiplexing?
|
|
|
|
|
|
Sub-resources of the job.
|
|
|
Session directory:
|
|
|
<base URL>/jobs/<job id>/session
|
|
|
- store, modify, retrieve files in session directory (PUT, GET, DELETE, maybe use POST for altering part of the file?)
|
|
|
- Multiplexing for bulk operation or provide alternative way to do everything through POST?
|
|
|
|
|
|
Information about job:
|
|
|
<base URL>/jobs/<job id>/control/<information type>
|
... | ... | |