On Mon, Feb 28, 2011 at 11:53 AM, Danushka Menikkumbura <[email protected]>wrote:
> Srinath, > > That was not for topics but for queues. What is the approach for queues? > I need to check on that. Anyway as I see what Amila has suggested is the > proper approach. Also (something that just popped into my mind) Qpid has > client id as part of its connection url which has no apparent use. I need to > check if we can use that as our tenant id so that we can use queue/topic > names as it is. > The normal convention for multitenacy is that users use the user name as userName@tenatdomain when the want to access the system as a tenant. Other are same. so in Qpid case if a user wants to access a queue or topic he sends his queue or topic name with the tenant specific name i.e [email protected] Qpid should internally handle the proper queue/topic map. thanks, Amila. > > Thanks, > Danushka > > On Mon, Feb 28, 2011 at 7:11 AM, Srinath Perera <[email protected]> wrote: > >> As I recall, we were discussing about Qpid MT with design meetings. >> Danushaka, what was the conclusion of those discussions? did we >> implement it? >> --Srinath >> >> 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. >> > >> > 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. >> > >> > 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 >> > >> > >> >> >> >> -- >> ============================ >> Srinath Perera, Ph.D. >> Senior Software Architect, WSO2 Inc. >> Visiting Lecturer, University of Moratuwa >> Member, Apache Software Foundation >> Research Scientist, Lanka Software Foundation >> Blog: http://srinathsview.blogspot.com/ >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
