[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-275) Move Selector processing IN the Channel

[Tim Fox (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-275?page=comments#action_12340484 ] 
            
Tim Fox commented on JBMESSAGING-275:
-------------------------------------

I have split the work for this task into two subtasks-

One to to implement the iteration in memory (the main part)

The other to implement the indexes and make sure it works with paging.

> Move Selector processing IN the Channel
> ---------------------------------------
>
>                 Key: JBMESSAGING-275
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-275
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Messaging Core
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.2.0.Alpha1
>
>   Original Estimate: 2 weeks
>  Remaining Estimate: 2 weeks
>
> Currently, a consumer "arrests" a message that is being handled to it and doesn't match the Selector. That means it returns an active Delivery for it, but it doesn't forward the message to the client. This is because the consumer needs to be able to receiver further messages coming after the non-matching message, and that may potentially match the selector.
> This is a poor solution that doesn't scale. We may end up with lots of non-matching messages being "arrested" by a consumer, while they could just be simply returned to the channel and forwarded to other potential consumers.
> A possible (right) approach is to move selector processing in the Channel, so the message is not even handled to the non-accepting cosumer. Review this and refactor.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira