On Fri, Sep 14, 2012 at 5:40 PM, Pradeep Fernando <[email protected]> wrote:
> Hi all, > > agree with the versioning and p2 repo issues. But when it comes to the > actual effort that needs to be put in to carry out this refactoring : > *trivial*. > > You just have to replace the, > > SuperTenantCarbonContext class with PrivilegedCarbonContext > replace usage of CarbonContextHolder with CarbonContext. > I think the effort mainly on creating new components with the version. If this is just a find an replacement, why don't we deprecate the existing SuperTenantCarbonContext and CarbonContextHolder classes and call the correct functions from that? This solves the performance and other issues. >From 4.1.0 or next major release we can drop those deprecated methods and change other components. thanks, Amila. > > This is basically a find and replace across platform. This wont affect > the stability of the platform either, as we are not doing any drastic > changes to the usage. However Once the refactoring is done, > > the pros include : > > cleaner API - earlier it was only senaka who could decrypt this API. :) > performance enhancements due to minimal delegations. > This will also help our efforts of introducing pooling/optimizations > in this space. - targeting stratos > > > if the people are so concerned about versioning incompatibilities, we > could always go for a 4.1.0 > > thanks, > --Pradeep > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
