On Sun, Feb 27, 2011 at 7:12 PM, Amila Suriarachchi <[email protected]> wrote:
> hi, > > Shammi has started the $subject since registry required the multi tenancy > support and there is time > to finish this before end of march. > That's great. > > Event Multi tenant has two parts > > 1. multi tenating topics and subscriptions stored in registry. > This can be done by using the tenant specific registry to store and > retrieve topics/subscriptions. > +1 for this approach. Thanks, Senaka. > > 2. Qpid multi tenancy > I think Qpid does not support multi tenancy. so the possible way of > achieving multi tenancy is to append the domain name to > topic name then actual topics names would appear as follows. > > wso2.com/myTopic > ibm.com/myTopic > > But this gives a problem for the users who directly going to connect to > Qpid server. > now users need to given the topic name with the domain name. > > But a better solution would be to give the tenant domain with the user name > and internally qpid authenticate the user and > create the actually queue name. > > i.e a user will subscribe as > > [email protected] to myTopic > internally qpid process the user name and actually subscribes to > wso2.com/myTopic. > > Danushka, is it possible to do this? If so I think even the carbonEvent > compoent can use this convention which I belive is the best way. > > thanks, > Amila. > > > > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
