[
https://issues.apache.org/jira/browse/QPID-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440281#comment-13440281
]
michael j. goulish commented on QPID-4241:
------------------------------------------
Here is the proposed functional specification.
proposed functional specification
{
purpose
{
Some users need browse-only functionality. For example,
messages represent the an ongoing history of events,
all of which are relevant to newly joining consumers.
The messages should remain unconsumed and available to
newcomers until they are outdated by time-to-live rules,
thrown away by a ring-queue, or the queue is destroyed.
}
strategy note
{
ACL and browse-only-queue solutions to this problem are
both possible. But right now we should prefer a
browse-only-queue solution, because
(1) it would satisfy the current customer's requirements, and
(2) the ACL functionality requires a complete overhaul.
}
user interface
{
1. extend x-declare{arguments:{}} in our addressing
to include 'browse-only'.
2. queues that are declared "browse-only" will allow
subscribers to access queues, and 'acquire' messages
normally -- but that 'acquisition' in this queue would
result in only a browse. The message would remain.
3. no effect on ACLs.
}
testing
{
As user mick, use standard command line tools to:
1. declare a queue with browse-only argument.
2. use standard command line tool to send N
messages to the queue.
3. use standard tool to 'consume' messages from
queue. Confirm that N messages are read.
4. Repeat step 3 at least once, and confirm that
same N messages are again read every time.
( They are not consumed. )
5. Set TTL on messages and confirm that it removes
messages from queue.
6. Confirm same behavior across all queue types.
}
}
> browse-only queues
> ------------------
>
> Key: QPID-4241
> URL: https://issues.apache.org/jira/browse/QPID-4241
> Project: Qpid
> Issue Type: New Feature
> Components: C++ Broker
> Affects Versions: Future
> Reporter: michael j. goulish
> Assignee: michael j. goulish
>
> Some users need browse-only functionality. For example, messages represent
> the an ongoing history of events, all of which are relevant to newly joining
> consumers. The messages should remain unconsumed and available to newcomers
> until they are outdated by time-to-live rules, or the queue is destroyed.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
