You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Henry Saginor (JIRA)" <ji...@apache.org> on 2019/04/24 21:46:00 UTC

[jira] [Updated] (OAK-8275) Add NIO channel access to JCR binaries.

     [ https://issues.apache.org/jira/browse/OAK-8275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henry Saginor updated OAK-8275:
-------------------------------
    Description: 
This is a follow up to the discussion started in OAK-8186. Currently JCR binaries can only be accessed via InputStream. This is often inefficient with modern Java applications and libraries. The proposal is to add API that returns SeekableByteChannel

Here is one possible implementation -
 [https://github.com/apache/jackrabbit-oak/compare/trunk...hsaginor:createChannel2]

  was:
This is a follow up to the discussion started in OAK-8186. Currently JCR binaries can only be accessed via InputStream. This often inefficient with modern Java applications and libraries. The proposal is to add API that returns SeekableByteChannel

Here is one possible implementation -
https://github.com/apache/jackrabbit-oak/compare/trunk...hsaginor:createChannel2


> Add NIO channel access to JCR binaries.
> ---------------------------------------
>
>                 Key: OAK-8275
>                 URL: https://issues.apache.org/jira/browse/OAK-8275
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Henry Saginor
>            Priority: Major
>
> This is a follow up to the discussion started in OAK-8186. Currently JCR binaries can only be accessed via InputStream. This is often inefficient with modern Java applications and libraries. The proposal is to add API that returns SeekableByteChannel
> Here is one possible implementation -
>  [https://github.com/apache/jackrabbit-oak/compare/trunk...hsaginor:createChannel2]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)