Hi Amani, Alright, but why can't we store that application context information inside the Carbon Context itself. That would reduce the setup overhead by half.
Thanks, Senaka. On Tue, Sep 11, 2012 at 6:49 AM, Amani Soysa <am...@wso2.com> wrote: > Hi Senaka, > > On Mon, Sep 10, 2012 at 10:33 PM, Senaka Fernando <sen...@wso2.com> wrote: > >> Hi Amani, >> >> I found that CarbonApplicationContext was added in r128928. What's this >> used for? >> >> >> CarbonApplicationContext is currently used in URL mapper component and >> logging component. This is used to store application specific information, >> such as applicationName at a given instance, so we can get application >> specific logs by starting the application flow (just like start tenant >> flow). and also we use this for URL Mapper component where we keep URL >> mapping (host) VS actual URL(long url) of a given application. Therefore we >> thought of having a seperate CarbonApplicationContext. >> This can be further used for Application specific stuff for later use. >> >> >> Regards, > Amani > > >> Thanks, >> Senaka. >> >> On Mon, Sep 10, 2012 at 8:48 PM, Afkham Azeez <az...@wso2.com> wrote: >> >>> >>> >>> On Mon, Sep 10, 2012 at 8:29 PM, Senaka Fernando <sen...@wso2.com>wrote: >>> >>>> +1, I believe that we're already on it, :). >>>> >>>> So Azeez, in the context of the perf improvements, what's the >>>> CarbonApplicationContext? Can't we replace it with CarbonContext. >>>> >>> >>> I'm not familiar with CarbonApplicationContext, but the idea is to get >>> rid of all the Carbon*Context* classes, and have only CarbonContext, or >>> just SupertenantCarbonContext & CarbonContext. >>> >>> >>> >>>> Also, are people actually reusing CarbonContext from >>>> ConfigurationContext, AxisService, MessageContext, HTTPSession etc? or is >>>> it only thread-local? We can easily refactor if we can find answers to >>>> these. >>>> >>>> Regards, >>>> Senaka. >>>> >>>> >>>> On Mon, Sep 10, 2012 at 8:25 PM, Pradeep Fernando <prad...@wso2.com>wrote: >>>> >>>>> noted. lets do it. >>>>> >>>>> --Pradeep >>>>> >>>> >>>> >>>> >>>> -- >>>> *Senaka Fernando* >>>> Member - Integration Technologies Management Committee; >>>> 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://linkedin.com/in/senakafernando >>>> >>>> * >>>> Lean . Enterprise . Middleware >>>> >>>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **az...@wso2.com* <az...@wso2.com>* 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* >>> >>> >> >> >> -- >> *Senaka Fernando* >> Member - Integration Technologies Management Committee; >> 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://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> > -- *Senaka Fernando* Member - Integration Technologies Management Committee; 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://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
