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

Reply via email to