[
https://issues.apache.org/jira/browse/QPID-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenta lee updated QPID-1766:
-----------------------------
Attachment: selector.patch
Thank you Gordan, I fixed the locking bug.
And Carl mention me that I still use popAnddequeue in Queue::consumNextMessage.
I also fixed this.
I found out that the field "Message& msg" in Queue::seek function is
unnecessary. Because I already pass an iterator into it. So I did some
modification.
However, I am curious about why do we need another message variable in
popAndDequeue. Can't we just dequeue it first and then pop the message?
Because I am not sure if store->dequeue will modify the queue so I did the same
way in earseAndDequeue.
> Implemention of selector using Xquery
> -------------------------------------
>
> Key: QPID-1766
> URL: https://issues.apache.org/jira/browse/QPID-1766
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, C++ Client
> Environment: Linux
> Reporter: chenta lee
> Attachments: Makefile.patch, selector.patch, selector.patch,
> selector_client.patch, selector_example.zip
>
>
> I implemented the message selector for C++ broker and client using Xquery.
> I will attach an example later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
