[
https://issues.apache.org/jira/browse/QPID-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894134#comment-15894134
]
Keith Wall commented on QPID-7618:
----------------------------------
Hi Alex,
As discussed - a couple of comments on UI consistency:
* Queue tab
** we use queue "depth" and queue "size" interchangeable. Suggest we
standardise on the former.
** the presentation of "Maximum Queue Depth" attribute should follow Size
attribute i.e. <queue depth messages> : ( <queue depth bytes>)
** drop "Size" attribute from RHS
** rename "Size including header" to simply "Size" (Depth in the parlance).
** Message table - rename "Size" to "Payload size".
* Queue edit dialoge
** Remove words "including headers"
* Message dialogue
** Rename field "Size" to "Payload Size"
> Ring policy type
> ----------------
>
> Key: QPID-7618
> URL: https://issues.apache.org/jira/browse/QPID-7618
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Affects Versions: qpid-java-6.1.1, qpid-java-7.0
> Reporter: Tomas Vavricka
> Assignee: Keith Wall
> Labels: policy-type, queue, ring
> Fix For: qpid-java-7.0
>
> Attachments: 0001-QPID-7569-Ring-policy-type.patch
>
>
> It would be good if Java Broker will support ring policy.
> Ring policy - delete oldest message(s) when queue capacity is reached
> Queue capacity can be defined by maximum count of message and maximum size of
> messages (including header).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
