Alan Conway commented on DISPATCH-803:

I want to back up a bit, I think my suggestion was not right. The original 
requirement is to prevent auto-creation of addresses. This proposal sounds like 
the router will auto-create *forbidden* addresses which is quite different: Not 
auto-creating address X means client connecting/sending to X gets a 'not-found' 
error.  Creating X with {distribution=forbidden} creates a permanently unusable 
address named X, which would have to be explicitly deleted or modified to use 
it later.  We could make a special case meaning for 
defaultDistribution=forbidden but that is confusing. I think separate config is 

autoLink = True|False # default True
autoCreateDistribution # default balanced

With these two attributes we don't need "forbidden" for this JIRA (but can 
still introduce it later if we want to)

Sorry for leading the conversation astray. 

> refuse attach to undefined addresses
> ------------------------------------
>                 Key: DISPATCH-803
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-803
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>            Reporter: Gordon Sim
>            Assignee: Ganesh Murthy
>             Fix For: 1.0.0
> At present, if you attach to an address in the router whose semantics have 
> not been specifically defined, you get balanced message routing semantics.
> It would be useful to be able to configure the router such that it would 
> refuse links whose source/target was not explicitly defined. E.g. by being 
> able to configure the default semantics to be of type 'invalid' (or anything 
> similar). (Being able to explicitly blacklist certain addresses might also be 
> nice, but is a more exotic use case I think).
> Messages sent through an anonymous link to these 'invalid' addresses would be 
> rejected.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to