Changeset 200

Timestamp:

03/23/06 08:37:50 (2 years ago)

Author:

dsandler

Message:

During node connection, distinguish transient errors (e.g. bad bootstrap)
which result in the client retrying the join, and actual errors which halt the
join process for good. (Note that there are now three kinds of errors:
"retrying", "error", and "fatal" -- the latter will cause the application to
exit immediately. Maybe the fatal should be removed, and the exit behavior
pushed up to whatever program is observing the client's operation.)

Also fixed a bug: Once the client starts, the status should be RUNNING, not
STARTING!

Files:

• feedtree/trunk/src/net/feedtree/core/client/Client.java (modified) (4 diffs)

feedtree/trunk/src/net/feedtree/core/client/Client.java

@@ -125 +125 @@
-        public static final int STATUS_NOT_STARTED = 0;
-        public static final int STATUS_STARTING = 1;
+        public static final int STATUS_RETRYING = 2;
-        public static final int STATUS_RUNNING = 1000;
-        public static final int STATUS_ERROR = -1;
@@ -343 +344 @@
-                } catch (java.io.StreamCorruptedException exc) {
-                    Logger.global.severe("Stream corruption error while finding bootstrap.  Sleeping and trying again.");
-ERROR
+RETRYING
-                            "Network error; re-trying");
-
@@ -404 +405 @@
-                            Logger.global.info("[Failed to bootstrap node into network after 60 sec.  Scrapping node and re-starting in 5-15 sec.]");
-
-ERROR
+RETRYING
-                                    "Failed to connect; re-trying shortly");
-
@@ -425 +426 @@
-        }
-        
-START
+RUNN
-                "FeedTree client ready");
-