You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2017/10/13 15:58:00 UTC

[jira] [Updated] (QPID-7832) Refactor store/protocol API using Collection

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

Lorenz Quack updated QPID-7832:
-------------------------------
    Attachment: 0001-QPID-7832-Java-Broker-Refactor-store-protocol-API-us.patch

> Refactor store/protocol API using Collection<QpidByteBuffers>
> -------------------------------------------------------------
>
>                 Key: QPID-7832
>                 URL: https://issues.apache.org/jira/browse/QPID-7832
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>            Priority: Minor
>             Fix For: qpid-java-broker-7.0.0
>
>         Attachments: 0001-QPID-7832-Java-Broker-Refactor-store-protocol-API-us.patch
>
>
> Store/protocol APIs have gradually been evolving to accept/return message content/message metadata in terms of an ordered list of QBBs.  This has lead to use of helper methods such as those in QBBUtils which read from a list of buffers rather than a single one.
> This would be better refactored.   QpidByteBuffer should be an interface.  This would allow a concrete implementation CompositeQpidByteBuffer which is backed by a list produced by the store or network IO.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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