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

Robbie Gemmell updated PROTON-1767:
-----------------------------------
    Summary: allow the Transport to expose an output buffer that is not 
read-only  (was: [proton-j] Allow the Transport to expose an output buffer that 
is not read-only)

> allow the Transport to expose an output buffer that is not read-only
> --------------------------------------------------------------------
>
>                 Key: PROTON-1767
>                 URL: https://issues.apache.org/jira/browse/PROTON-1767
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-j
>    Affects Versions: proton-j-0.25.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: proton-j-0.26.0
>
>
> In some cases the read-only output buffer exposed by TransportImpl by calling 
> head() or getOutputBuffer() can lead to extra intermediate copies of the 
> buffer based on the IO framework being used to transmit the bytes (such as 
> current Netty releases).  This is due to the fact that the read-only buffer 
> reports that it doesn't have a backing array so the frameworks try to work 
> around this to optimize the transfer of bytes.  For uses who are aware of 
> this and can ensure they never tamper with the buffer contents that aren't 
> consumed we should let them choose to expose a writable duplicate of the 
> output buffer.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to