[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Algorithm broken in WildcardAddressManager

[timfox]

"ataylor" wrote : ok, so instead of adding a mapping for an address when the first binding is added we do this for each allowable address.
  | 

Allowable addresses are only used if checkAllowable = true.

It's valid for the postoffice to have no allowable addresses, and wildcards must work then too.

Checkallowable is really only true for JMS, where we have to trap sends to non-existent topics.

anonymous wrote : 
  |  for queues this is no different as its always added anyway, but for topics there'll be a mapping which contains an empty bindings object. This means that when a new consumer registers with a wildcard queue i can garauntee that theres always a mapping to check. so lets say the wildcard topic is topicjms.topic.* i can search the mappings to make sure that binding topicjms.topic.A also gets this binding registered with it. 
  | 

That works if the queue already exists at the time the wildcard subscription is added. But what if the queue is added *after* the subscription is added?

anonymous wrote : 
  | Before i couldn't do this which is why i was pre calculating the whole map.
  | 
  | actually come to think of it, we could remove allowable destinations completely and for containsDestination we could just use the keyset of the mappings.

Only if we only allow routing to allowable addresses at all times (I.e. effectively force checkAllowable to always be true)

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

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