On Sat, Sep 18, 2010 at 2:15 PM, Supun Kamburugamuva <[email protected]> wrote:
> On Fri, Sep 17, 2010 at 4:58 PM, Ruwan Linton <[email protected]> wrote: > > Hmmm, I didn't get it. A component initialization, (which will happen > > most of the time inline with the system initialization) and a tenant > > initialization are 2 different things. > > > > A particular component would want to initialize itself at the system > > initialization while it might want to do certain task for each and every > > tenant when it is initializing. Note that all tenants are using the same > > instance of a given component. > > > We can create work arounds and get rid of these problems. For example > now proxy observer is created inside the stratos synapse management > component. But these are ugly and in the long term hard to maintain. > Please show me your code tomorrow. Perhaps you are doing things incorrectly. I believe, the model we have in place is clean and maintainable. > > Thanks, > Supun.. > > > > Ruwan > > > > On 9/17/10 2:22 PM, Srinath Perera wrote: > >> +1 > >> > >> On Fri, Sep 17, 2010 at 2:16 PM, Supun Kamburugamuva<[email protected]> > wrote: > >>> I'm looking for way for a component to know when it has to initialize > >>> and when it has to destroy? > >>> > >>> At the moment we have two instances where a component should > initialize. > >>> > >>> 1. Carbon initialization > >>> 2. Tenant initialization > >>> > >>> But these two are two different cases. From a component perspective > >>> they shouldn't know weather it is a system initialization or a tenant > >>> initialization. It would be great to have a unified mechanism across > >>> the platform for a component to decide when to initialize and when to > >>> destroy. > >>> > >>> Thanks, > >>> > >>> -- > >>> Supun Kamburugamuva > >>> Technical Lead > >>> WSO2 Inc.; http://wso2.org > >>> E-mail: [email protected]; Mobile: +94 77 431 3585 > >>> Blog: http://supunk.blogspot.com > >>> > >>> _______________________________________________ > >>> Carbon-dev mailing list > >>> [email protected] > >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >>> > >> > >> > > > > > > -- > > Ruwan Linton > > Software Architect& Product Manager, WSO2 ESB; http://wso2.org/esb > > WSO2 Inc.; http://wso2.com > > > > Lean . Enterprise . Middleware > > > > phone: +1 408 754 7388 ext 51789 > > email: [email protected]; cell: +94 77 341 3097 > > blog: http://blog.ruwan.org > > linkedin: http://www.linkedin.com/in/ruwanlinton > > tweet: http://twitter.com/ruwanlinton > > > > > > _______________________________________________ > > Carbon-dev mailing list > > [email protected] > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > -- > Supun Kamburugamuva > Technical Lead > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 431 3585 > Blog: http://supunk.blogspot.com > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- *Afkham Azeez* Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, * * *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/> * email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
