Commit a2a4aa35 authored by Grégory Wisniewski's avatar Grégory Wisniewski

Remove dealWithClientFailure from the base storage event handler class and it's

call because the implementation do nothing. This is used only in
ClientEventHandler and so, no overloading is required.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1089 71dcc9de-d417-0410-9af5-da40c76e7ee4
parent 27de0880
...@@ -27,9 +27,7 @@ from neo.exception import PrimaryFailure, OperationFailure ...@@ -27,9 +27,7 @@ from neo.exception import PrimaryFailure, OperationFailure
class BaseStorageHandler(EventHandler): class BaseStorageHandler(EventHandler):
"""This class implements a generic part of the event handlers.""" """This class implements a generic part of the event handlers."""
pass
def dealWithClientFailure(self, uuid):
pass
class BaseMasterHandler(BaseStorageHandler): class BaseMasterHandler(BaseStorageHandler):
...@@ -68,10 +66,6 @@ class BaseMasterHandler(BaseStorageHandler): ...@@ -68,10 +66,6 @@ class BaseMasterHandler(BaseStorageHandler):
self.app.shutdown() self.app.shutdown()
elif state == HIDDEN_STATE: elif state == HIDDEN_STATE:
raise OperationFailure raise OperationFailure
elif node_type == CLIENT_NODE_TYPE and state != RUNNING_STATE:
# XXX: check why dealWithClientFailure is triggered with node
# notification and not only by client connection failure
self.dealWithClientFailure(uuid)
class BaseClientAndStorageOperationHandler(BaseStorageHandler): class BaseClientAndStorageOperationHandler(BaseStorageHandler):
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment