Annoyingly, ClientObserver.clientDidLogoff() is called before the client's

inner bits are all clear and ready to try logging on to a new server. We
specifically wait to call clientLogonFailed() until after everything is
cleared, but I don't want to change the behavior of clientDidLogoff() for fear
that any one of the zillion directors depends on something being around during
that call.

Instead I added another callback clientDidClear() that is called when a
successful session is fulled cleared out (basically when we're not calling
clientLogonFailed()) so that entities that are waiting for a logoff to finish
so that they can logon somewhere else have a clean way of doing so.


git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@4255 542714f4-19e9-0310-aa3c-eee0fc999fb1

tests/src/java/com/threerings/crowd/client/TestClient.java

@@ -120,6 +120,10 @@ public class TestClient
         System.exit(0);
     }
 
+    public void clientDidClear (Client client)
+    {
+    }
+
     protected CrowdContext createContext ()
     {
         return new CrowdContextImpl();