[ 
https://issues.apache.org/jira/browse/PROTON-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874811#comment-15874811
 ] 

ASF GitHub Bot commented on PROTON-1409:
----------------------------------------

GitHub user clebertsuconic opened a pull request:

    https://github.com/apache/qpid-proton-j/pull/7

    PROTON-1409 Exposing delivery length

    This is to expose the delivery length to allow creating the buffer with the 
required bytes only
    
    https://issues.apache.org/jira/browse/PROTON-1409

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/clebertsuconic/qpid-proton-j proton-1409

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-proton-j/pull/7.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #7
    
----
commit 953f0aee9cc5ce95f80cb2a9c1f3628c07429605
Author: Clebert Suconic <[email protected]>
Date:   2017-02-17T03:29:02Z

    PROTON-1409 Exposing delivery length
    
    This is to expose the delivery length to allow creating the buffer with the 
required bytes only
    
    https://issues.apache.org/jira/browse/PROTON-1409

----


> Expose delivery size
> --------------------
>
>                 Key: PROTON-1409
>                 URL: https://issues.apache.org/jira/browse/PROTON-1409
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-j
>            Reporter: clebert suconic
>
> When I'm receiving the Delivery on the broker, I have to pre-create a buffer 
> to copy the byte array inside the Delivery.
> I would like to have it exposed so I only allocated the required bytes.
> I will follow up with a PR on this



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to