You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <ji...@apache.org> on 2011/02/21 13:01:38 UTC

[jira] Resolved: (QPID-2104) Improved LVQ implementation

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

Gordon Sim resolved QPID-2104.
------------------------------

    Resolution: Fixed

> Improved LVQ implementation
> ---------------------------
>
>                 Key: QPID-2104
>                 URL: https://issues.apache.org/jira/browse/QPID-2104
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>    Affects Versions: 0.5
>            Reporter: Gordon Sim
>            Assignee: Gordon Sim
>             Fix For: 0.9
>
>
> My view of what ideal 'LVQ' behaviour would be like is that the 'queue'
> would really be more like a 'topic' where the last message for each key was
> always saved. Clients would subscribe to it and receive the last message
> published for each key and subsequently any updates (i.e. any new messages). I.e. the consumers are always non-competing.
> Rob Godfrey also points out that if subscribers fall behind they need only be sent the latest for every key (i.e. any superceded values  can be skipped).

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org