Uploaded image for project: 'OASIS Content Management Interoperability Services (CMIS) TC'
  1. OASIS Content Management Interoperability Services (CMIS) TC
  2. CMIS-809

Asynchronous Processing

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: New
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Domain Model
    • Labels:
      None
    • Proposal:
      Hide

      This is a proposal for asynchronous processing of content streams and renditions. It also proposes to support the generation of renditions dynamically according to a specification rather than selecting a rendition from an existing supported collection of renditions. There are actually two proposals.

      The first proposal introduces a status monitor object: https://www.oasis-open.org/apps/org/workgroup/cmis/download.php/57765/dynamicRenditionAndAsynchronousWithMonitors.docx

      The second proposal does not use status monitor objects: https://www.oasis-open.org/apps/org/workgroup/cmis/download.php/57758/dynamicRenditionAndAsynchronousProcessing.docx

      Status monitor objects are more general because they allow for any request to be asynchronous. However, it was felt that creating a new object for status monitoring would introduce too much overhead to asynchronous processing.

      The HTTP binding would need to be extended to allow for asynchronous processing, and a proposed HTTP binding for this purpose is in https://www.oasis-open.org/apps/org/workgroup/cmis/download.php/57766/httpBindingForAsynchronousProcessing.docx

      Show
      This is a proposal for asynchronous processing of content streams and renditions. It also proposes to support the generation of renditions dynamically according to a specification rather than selecting a rendition from an existing supported collection of renditions. There are actually two proposals. The first proposal introduces a status monitor object: https://www.oasis-open.org/apps/org/workgroup/cmis/download.php/57765/dynamicRenditionAndAsynchronousWithMonitors.docx The second proposal does not use status monitor objects: https://www.oasis-open.org/apps/org/workgroup/cmis/download.php/57758/dynamicRenditionAndAsynchronousProcessing.docx Status monitor objects are more general because they allow for any request to be asynchronous. However, it was felt that creating a new object for status monitoring would introduce too much overhead to asynchronous processing. The HTTP binding would need to be extended to allow for asynchronous processing, and a proposed HTTP binding for this purpose is in https://www.oasis-open.org/apps/org/workgroup/cmis/download.php/57766/httpBindingForAsynchronousProcessing.docx

      Description

      Renditions and content streams may require a substantial amount of time to generate. It would therefore be useful to allow requests for content streams and renditions to be asynchronous. For example, asynchronous processing would allow a browser interface to have a progress bar.

        Attachments

          Activity

            People

            • Assignee:
              kenb Ken Baclawski (Inactive)
              Reporter:
              kenb Ken Baclawski (Inactive)
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: