You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2018/08/09 12:51:00 UTC
[jira] [Commented] (JCR-4355) Javadoc fixes and improvements for
new direct binary access API
[ https://issues.apache.org/jira/browse/JCR-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16574801#comment-16574801 ]
Julian Reschke commented on JCR-4355:
-------------------------------------
Alex' proposed patch: https://issues.apache.org/jira/secure/attachment/12934971/JCR-4355.diff
> Javadoc fixes and improvements for new direct binary access API
> ---------------------------------------------------------------
>
> Key: JCR-4355
> URL: https://issues.apache.org/jira/browse/JCR-4355
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-api
> Reporter: Alexander Klimetschek
> Priority: Major
> Attachments: JCR-4355.diff
>
>
> Here are some changes to the javadocs for the new API: OAK-7569-api-javadoc-improvements.patch
> * more concise descriptions
> * correcting some inaccuracies (clients cannot choose whether to do single or multipart upload, multipart might be strictly required depending on the size)
> * most importantly the upload algorithm (standard partSize calculation was wrong)
> * focus on API users, separated notes to implementors
> * for BinaryDownloadOptions added note from which jcr properties a client would normally take these values from
> * added security considerations
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)