incubator-awf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Stevenson (Moved) (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (AWF-146) Use FileChannel.transferTo() instead of MappedByteBuffer
Date Wed, 29 Feb 2012 10:10:09 GMT

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

Tony Stevenson moved DEFT-185 to AWF-146:
-----------------------------------------

        Fix Version/s:     (was: 0.4.0)
          Component/s:     (was: Core)
           Issue Type: Bug  (was: New Feature)
    Affects Version/s:     (was: 0.4.0)
                  Key: AWF-146  (was: DEFT-185)
              Project: Apache AWF  (was: Deft)
    
> Use FileChannel.transferTo() instead of MappedByteBuffer
> --------------------------------------------------------
>
>                 Key: AWF-146
>                 URL: https://issues.apache.org/jira/browse/AWF-146
>             Project: Apache AWF
>          Issue Type: Bug
>            Reporter: Séven Le Mesle
>            Assignee: Séven Le Mesle
>
> Using a MappedByteBuffer to deliver static content is not good as we can not use kernel
sendFile directive when available.
> The FileChannel.transferTo() allows for such a feature and would be far better. Even
notice that MappedByteBuffer is memory consuming, with transferTo() on his side is light and
efficient (no buffers involved for many OS). 
> The only backside is that we need to take great care of the opened files !
> Work would be to replace MBB stuff with the transferTo call and store a FileInputStream
as key attachment, the underlying FileChannel can be used to maintain position.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message