On Mon, Aug 9, 2010 at 4:11 PM, Supun Kamburugamuva <[email protected]> wrote:

> How about?
>
> failsafe.mode=all | none | endpoints | proxyservices
>

This is also fine. Only issue is if we introduce the failsafe mode to some
other functional component in the future, we will not be able to speicy
subsets properly. For an example say we introduce this to sequences. Then
how can we say enable fail safe mode for sequences and proxy services but
not for endpoints?

However I believe this is not a major concern now. So I'm ok with this.

Thanks,
Hiranya


>
> Thanks,
> Supun..
>
> On Tue, Aug 10, 2010 at 1:21 AM, Hiranya Jayathilaka <[email protected]>
> wrote:
> > Hi,
> >
> > On Mon, Aug 9, 2010 at 11:25 AM, Kasun Indrasiri <[email protected]> wrote:
> >>
> >>
> >> On Mon, Aug 9, 2010 at 3:09 PM, Samisa Abeysinghe <[email protected]>
> wrote:
> >>>
> >>>
> >>> On Mon, Aug 9, 2010 at 1:43 PM, Kasun Indrasiri <[email protected]>
> wrote:
> >>>>
> >>>> These are the combinations.
> >>>> - Fail-safe mode enabled Endpoints : failsafe.mode.enable=endpoints
> >>>> - Fail-safe mode enabled Proxy Services
> >>>> : failsafe.mode.enable=proxyservices
> >>>> - enable/disable for all : : failsafe.mode.enable=true/false
> >>>> We can disable it for Endpoints and enable it for Proxy services and
> >>>> vice versa.
> >>>
> >>> Can I enable for a particular endpoint or a particular proxy service?
> >>> From the syntax, it sounds it is not possible. Would we want to do
> that?
> >>
> >> No. We can't  use 'failsafe.mode.enable' configuration to handle
> >> individual Proxy Services/EPs failures.
> >>>
> >>> Anyway, in the syntax
> >>> failsafe.mode.enable=[true/false/endpoints/proxyservices] # defaults to
> >>> true
> >>> given that we use names for proxies and endpoints, true and false does
> >>> seem out of place. What if we replace true with all meaning both
> proxies and
> >>> endpoints and false with none?
> >>> failsafe.mode.enable=[all/none/endpoints/proxyservices] # defaults to
> all
> >>
> >> +1 for -  failsafe.mode.enable=[all/none/endpoints/proxyservices] #
> >> defaults to all
> >>
> >>>
> >>>
> >>> Also what if I have both
> >>> failsafe.mode.enable=endpoints
> >>> and
> >>> failsafe.mode.enable=proxyservices
> >>> set by the user? Do we treat that to be equal to
> >>> failsafe.mode.enable=endpoints
> >>> failsafe.mode.enable=all
> >>> Or do we consider only the last setting to be effective?
> >>
> >> Say, we have the following configuration :
> >> failsafe.mode.enable=all
> >> failsafe.mode.enable=endpoints
> >> failsafe.mode.enable=proxyservices
> >
> >
> > IMO this leads to lot of confusion. Why can't we just have two parameters
> > like:
> >
> > proxy.failsafe.mode
> > endpoint.failsafe.mode
> >
> > ??
> >
> > Thanks,
> > Hiranya
> >
> >>
> >> We consider that the last setting(i.e proxyservices) to be effective.
> (We
> >> should not encourage this kind of a config though :))
> >> Thanks.
> >> Kasun
> >>>>
> >>>> On Mon, Aug 9, 2010 at 12:24 PM, Samisa Abeysinghe <[email protected]>
> >>>> wrote:
> >>>>>
> >>>>>
> >>>>> On Mon, Aug 9, 2010 at 11:38 AM, Kasun Indrasiri <[email protected]>
> >>>>> wrote:
> >>>>>>
> >>>>>> By using 'failsafe.mode.enable' setting, we have to distinguish
> proxy
> >>>>>> services and endpoint fail-safety. So we need to have that
> configuration
> >>>>>> inside this property too. We can have something like this,
> >>>>>> failsafe.mode.enable=[true/false/endpoints/proxyservices] # defaults
> >>>>>> to true
> >>>>>
> >>>>> What are the combinations? Can we have it enabled for proxy services
> >>>>> but disabled for endpoints? What does it mean to say true, enable for
> all?
> >>>>>
> >>>>> Thanks,
> >>>>> Samisa...
> >>>>>
> >>>>> Samisa Abeysinghe
> >>>>> VP Engineering
> >>>>> WSO2 Inc.
> >>>>> http://wso2.com
> >>>>> http://wso2.org
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Carbon-dev mailing list
> >>>>> [email protected]
> >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Kasun Indrasiri
> >>>> Senior Software Engineer
> >>>> WSO2, Inc.; http://wso2.com
> >>>> lean.enterprise.middleware
> >>>>
> >>>> cell: +94 71 536 4128
> >>>> Blog : http://kasunpanorama.blogspot.com/
> >>>>
> >>>> _______________________________________________
> >>>> Carbon-dev mailing list
> >>>> [email protected]
> >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>>>
> >>> Thanks,
> >>> Samisa...
> >>>
> >>> Samisa Abeysinghe
> >>> VP Engineering
> >>> WSO2 Inc.
> >>> http://wso2.com
> >>> http://wso2.org
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Carbon-dev mailing list
> >>> [email protected]
> >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Kasun Indrasiri
> >> Senior Software Engineer
> >> WSO2, Inc.; http://wso2.com
> >> lean.enterprise.middleware
> >>
> >> cell: +94 71 536 4128
> >> Blog : http://kasunpanorama.blogspot.com/
> >>
> >> _______________________________________________
> >> Carbon-dev mailing list
> >> [email protected]
> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>
> >
> >
> >
> > --
> > Hiranya Jayathilaka
> > Senior Software Engineer;
> > WSO2 Inc.;  http://wso2.org
> > E-mail: [email protected];  Mobile: +94 77 633 3491
> > Blog: http://techfeast-hiranya.blogspot.com
> >
> > _______________________________________________
> > Carbon-dev mailing list
> > [email protected]
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: [email protected];  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________
Carbon-dev mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to