Hi Tharindu, On Fri, Sep 23, 2011 at 3:56 PM, Tharindu Mathew <[email protected]> wrote:
> Hi everyone, > > I believe many products have this requirement. How can we do $subject? > > I was thinking of storing task related configurations in the tenant's > registry. The task engine then executes the task only allowing access to > resources that the specific tenant has access to. > > WDYT? > I believe, you're referring to the schedule tasks component (pardon me if it's not). So here, If I'm not mistaken, this suggestion can be split into two main parts namely, 1. Multitenanting tasks (This is already available AFAIK) 2. Storing tasks related configurations in the registry. Delving into the second point, which is persisting task configurations in the registry, we too have this requirement for DSS and for the moment we accomplish this by handling it in DSS side (which might not be the best suited solution). A better solution would be to handle it in scheduled-tasks component itself. So, +1 for a better way to persist task configurations. > > -- > Regards, > > Tharindu > > blog: http://mackiemathew.com/ > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > Regards, -- Prabath Abeysekara Software Engineer WSO2 Inc. Email: [email protected] <[email protected]> Mobile: +94774171471 <http://harshana05.blogspot.com/>
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
