curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-248) Introduce pluggable error handlers
Date Sun, 06 Sep 2015 22:13:45 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733150#comment-14733150
] 

ASF GitHub Bot commented on CURATOR-248:
----------------------------------------

Github user cammckenzie commented on the pull request:

    https://github.com/apache/curator/pull/98#issuecomment-138130903
  
    Looks good to me Jordan. My only nit would be that the name ErrorPolicy doesn't really
convey what it's an error policy. Would ConnectionStateErrorPolicy or something like that
be more descriptive?


> Introduce pluggable error handlers
> ----------------------------------
>
>                 Key: CURATOR-248
>                 URL: https://issues.apache.org/jira/browse/CURATOR-248
>             Project: Apache Curator
>          Issue Type: Sub-task
>          Components: Framework, Recipes
>            Reporter: Jordan Zimmerman
>            Assignee: Jordan Zimmerman
>             Fix For: 3.0.0
>
>
> Currently, Curator recipes handle error conditions by listening for the SUSPENDED connection
state. Some users would like Curator to try to maintain the session if possible. Introduce
a pluggable error handler system. Have an implementation that does the current behavior. Create
another that attempts to wait until session lost.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message