Nixed premature optimization wherein a frequent premature optimizer, who we

will not name, was trying to allow certain authentications to proceed directly
on the authenticator thread instead of making a round trip through the
invoker. This resulted in those authentications trying to post their results
from the authenticator thread, which is bad because all downstream messages
should be posted from the distributed object thread.

The only authentications that would "benefit" from this optimization were peer
authentications of which there would be extremely few (currently one in our
largest installation) compared to the hundreds of thousands of normal
authentications, which have to make the invoker thread round trip as a matter
of course.


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

src/java/com/threerings/presents/server/DummyAuthenticator.java

@@ -32,20 +32,12 @@ import com.threerings.presents.server.net.AuthingConnection;
 import static com.threerings.presents.Log.log;
 
 /**
- * A simple authenticator implementation that simply accepts all
- * authentication requests.
+ * A simple authenticator implementation that simply accepts all authentication requests.
  */
 public class DummyAuthenticator extends Authenticator
 {
-    @Override
-    protected Invoker getInvoker ()
-    {
-        return null; // not needed
-    }
-
     // from abstract Authenticator
-    protected void processAuthentication (
-            AuthingConnection conn, AuthResponse rsp)
+    protected void processAuthentication (AuthingConnection conn, AuthResponse rsp)
         throws PersistenceException
     {
         log.info("Accepting request: " + conn.getAuthRequest());