[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: JCR-4355-v3-javadoc-html.zip > 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 > Fix For: 2.18 > > Attachments: JCR-4355-jr.diff, JCR-4355-v2-javadoc-html.zip, > JCR-4355-v2.patch, JCR-4355-v3-javadoc-html.zip, JCR-4355-v3.patch, > JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: (was: JCR-4355-v3-javadoc-html.zip) > 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 > Fix For: 2.18 > > Attachments: JCR-4355-jr.diff, JCR-4355-v2-javadoc-html.zip, > JCR-4355-v2.patch, JCR-4355-v3-javadoc-html.zip, JCR-4355-v3.patch, > JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: JCR-4355-v3.patch JCR-4355-v3-javadoc-html.zip > 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 > Fix For: 2.18 > > Attachments: JCR-4355-jr.diff, JCR-4355-v2-javadoc-html.zip, > JCR-4355-v2.patch, JCR-4355-v3-javadoc-html.zip, JCR-4355-v3.patch, > JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: (was: JCR-4355-v3-javadoc-html.zip) > 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 > Fix For: 2.18 > > Attachments: JCR-4355-jr.diff, JCR-4355-v2-javadoc-html.zip, > JCR-4355-v2.patch, JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: (was: JCR-4355-v3.patch) > 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 > Fix For: 2.18 > > Attachments: JCR-4355-jr.diff, JCR-4355-v2-javadoc-html.zip, > JCR-4355-v2.patch, JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: JCR-4355-v3-javadoc-html.zip JCR-4355-v3.patch > 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 > Fix For: 2.18 > > Attachments: JCR-4355-jr.diff, JCR-4355-v2-javadoc-html.zip, > JCR-4355-v2.patch, JCR-4355-v3-javadoc-html.zip, JCR-4355-v3.patch, > JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Julian Reschke updated JCR-4355: Attachment: JCR-4355-jr.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 >Assignee: Julian Reschke >Priority: Major > Fix For: 2.18 > > Attachments: JCR-4355-jr.diff, JCR-4355-v2-javadoc-html.zip, > JCR-4355-v2.patch, JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Julian Reschke updated JCR-4355: Fix Version/s: 2.18 > 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 >Assignee: Julian Reschke >Priority: Major > Fix For: 2.18 > > Attachments: JCR-4355-v2-javadoc-html.zip, JCR-4355-v2.patch, > JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: (was: JCR-4355-v2.patch) > 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-v2-javadoc-html.zip, JCR-4355-v2.patch, > JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: (was: JCR-4355-v2-javadoc-html.zip) > 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-v2-javadoc-html.zip, JCR-4355-v2.patch, > JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: JCR-4355-v2.patch JCR-4355-v2-javadoc-html.zip > 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-v2-javadoc-html.zip, JCR-4355-v2.patch, > JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: (was: JCR-4355-javadoc-html.zip) > 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-v2-javadoc-html.zip, JCR-4355-v2.patch, > JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: JCR-4355-v2-javadoc-html.zip > 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-v2-javadoc-html.zip, JCR-4355-v2.patch, > JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: JCR-4355-javadoc-html.zip > 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-v2-javadoc-html.zip, JCR-4355-v2.patch, > JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Attachment: JCR-4355-v2.patch > 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-v2.patch, JCR-4355.diff > > > Here are some changes to the javadocs for the new API: > [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Description: Here are some changes to the javadocs for the new API: [OAK-7569-api-javadoc-improvements.patch|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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 was: 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 > 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|https://issues.apache.org/jira/secure/attachment/12934364/12934364_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)
[jira] [Updated] (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:all-tabpanel ] Julian Reschke updated JCR-4355: Attachment: 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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Description: 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 was: 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 > 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 > > 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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Description: 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 was: 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 > 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 > > 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)
[jira] [Updated] (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:all-tabpanel ] Alexander Klimetschek updated JCR-4355: --- Description: 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 > 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 > > 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)
