[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: new QueueBrowser implementation

[timfox]

"ataylor" wrote : 
  | So first the PriorityLinkedList implementation will be changed to use ConcurrentLinkedQueue's instead of Lists. Doing this means that the server consumer can iterate over the queue without a comod exception being thrown. The only drawback is we can't add to the head so for now i'm just making a clone of the list.
  | 

I couldn't figure out from this if you're changing the implementation or just making a clone, since you say you're doing both in the same paragraph ;)

anonymous wrote : 
  | All browsing will be done using current consumer functionality. I'll add a new flag to specify what kind a consumer is, i.e. a browser or not. If a Consumer is a browser the it will not add itself to the queue to receive messages, instead it will iterate over the whole queue sending messages until there are no more.

How does this work with flow control? What if the consumer buffer is full before it has iterated the entire queue?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182138#4182138

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182138