[
https://issues.apache.org/jira/browse/CMIS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326010#comment-14326010
]
Florent Guillaume commented on CMIS-883:
----------------------------------------
Another option to communicate this information to the client would be to abuse
slightly the content type and return for instance a {{Content-Type:
application/pdf; incomplete=true}}. Parsers should be able to work with that.
> Asynchronous Rendition Retrieval
> --------------------------------
>
> Key: CMIS-883
> URL: https://issues.apache.org/jira/browse/CMIS-883
> 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 be 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
(v6.3.4#6332)
