chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Florian Müller (JIRA) <>
Subject [jira] [Commented] (CMIS-883) Asynchronous Rendition Retrieval
Date Fri, 16 Jan 2015 12:10:34 GMT


Florian Müller commented on CMIS-883:

That wouldn't be difficult to implement, but it would deviate from the CMIS specification.
Most CMIS clients wouldn't understand a 202 response and treat it as an error. There is also
no equivalent for the Web Services binding.  
But you may want start a discussion for the next CMIS specification version:

You could use some the rendition attributes to indicate that rendition is currently generated.
 For example, the length could be zero or you invent a new rendition kind that your clients
getContentStream could return a 0 bytes document while the generation takes place.

> Asynchronous Rendition Retrieval
> --------------------------------
>                 Key: CMIS-883
>                 URL:
>             Project: Chemistry
>          Issue Type: Improvement
>          Components: opencmis-server
>    Affects Versions: OpenCMIS 0.12.0
>            Reporter: Ron Gavlin
> Assume a CMIS client wants retrieve a high-fidelity PDF rendition of a large, volatile
Word document with minimal idle time. In this case, a standardized mechanism may bey needed
to inform the client that the rendition is 'not yet ready'. This scenario might occur, for
example, when the client is interfacing with a Linux-based CMIS server that forwards Word-to-PDF
conversion requests to a remote Windows server. Here, the rendition generation may take some
time to complete. 
> Would it make sense to send a standard '202 - Accepted' response code to the client to
indicate this 'rendition is not-yet-ready' condition? Once the rendition becomes available,
the rendition retrieval would return a standard 200 success response. Do you have other ideas
about how this use case might be supported in a standard way across CMIS servers?

This message was sent by Atlassian JIRA

View raw message