Because the currently existing carbon core project in crucible is named as ApacheDS-Core. And I used the same project to create a different review as this code also exists under carbon core.
On Tue, Nov 22, 2011 at 12:37 AM, Afkham Azeez <[email protected]> wrote: > Why is the link having the ID ApacheDS-Core? > > > On Mon, Nov 21, 2011 at 7:27 PM, Isuru Suriarachchi <[email protected]>wrote: > >> https://wso2.org/crucible/cru/ApacheDS-Core-3 >> >> >> On Mon, Nov 21, 2011 at 10:27 AM, Isuru Suriarachchi <[email protected]>wrote: >> >>> I didn't have much time for this during the weekend due to my exams. >>> Will send it today.. >>> >>> >>> On Mon, Nov 21, 2011 at 8:34 AM, Afkham Azeez <[email protected]> wrote: >>> >>>> Isuru, >>>> 2nd reminder. Send the Crucible link ASAP. >>>> >>>> >>>> On Sat, Nov 19, 2011 at 6:33 AM, Afkham Azeez <[email protected]> wrote: >>>> >>>>> Isuru, >>>>> Please create a Crucible project for the Ghost deployer feature & send >>>>> the link for review. Please add me as a reviewer. >>>>> >>>>> Thanks >>>>> Azeez >>>>> >>>>> >>>>> On Mon, Jul 18, 2011 at 10:50 AM, Isuru Suriarachchi >>>>> <[email protected]>wrote: >>>>> >>>>>> >>>>>> >>>>>> On Mon, Jul 18, 2011 at 12:06 AM, Afkham Azeez <[email protected]>wrote: >>>>>> >>>>>>> This is an idea I got for improving Stratos performance & optimizing >>>>>>> resource usage. Instead of loading all artifacts deployed by a tenant, >>>>>>> the >>>>>>> ghost deployers will create ghost services corresponding to the real >>>>>>> services. We will have a special type of Axis2 dispatcher which will >>>>>>> load >>>>>>> the real service, if not already deployed, and dispatch to that service. >>>>>>> This will reduce the memory consumption, as well as improve the response >>>>>>> times of the very first requests sent by the tenants. >>>>>>> >>>>>> >>>>>> So we'll have to disable all existing Axis2 deployers and enable only >>>>>> the ghost deployer by default. However it should create a dummy >>>>>> Axis2Service which has the same service name as the real service. And >>>>>> also >>>>>> it has to keep the file name of the real artifact. When the request comes >>>>>> in, we have to deploy the real service programmetically by calling the >>>>>> appropriate deployer and dispatch the request. >>>>>> >>>>>> Is this the approach that you are suggesting? >>>>>> >>>>>> Thanks, >>>>>> ~Isuru >>>>>> >>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Afkham Azeez* >>>>>>> Director of Architecture; 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* >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Isuru Suriarachchi >>>>>> Technical Lead & Product Manager, WSO2 Application Server >>>>>> WSO2 Inc. http://wso2.com >>>>>> email : [email protected] >>>>>> blog : http://isurues.wordpress.com/ >>>>>> >>>>>> lean . enterprise . middleware >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Afkham Azeez* >>>>> Director of Architecture; 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* >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Afkham Azeez* >>>> Director of Architecture; 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* >>>> >>>> >>> >>> >>> -- >>> Isuru Suriarachchi >>> Technical Lead & Product Manager, WSO2 Application Server >>> WSO2 Inc. http://wso2.com >>> email : [email protected] >>> blog : http://isurues.wordpress.com/ >>> >>> lean . enterprise . middleware >>> >>> >> >> >> -- >> Isuru Suriarachchi >> Technical Lead & Product Manager, WSO2 Application Server >> WSO2 Inc. http://wso2.com >> email : [email protected] >> blog : http://isurues.wordpress.com/ >> >> 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: **[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* > > -- Isuru Suriarachchi Technical Lead & Product Manager, WSO2 Application Server WSO2 Inc. http://wso2.com email : [email protected] blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
