Further wired up the client side of the distributed object system. Removed

the facilities for fetching (without subscribing to) an object. This is
done extremely rarely and the user might as well just subscribe and
immediately unsubscribe because the dichotomy between fetching and
subscribing just served to overly complicate the internals for no good
reason.


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

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

@@ -1,5 +1,5 @@
 //
-// $Id: PresentsServer.java,v 1.4 2001/06/01 22:12:03 mdb Exp $
+// $Id: PresentsServer.java,v 1.5 2001/06/09 23:39:04 mdb Exp $
 
 package com.threerings.cocktail.cher.server;
 
@@ -8,6 +8,8 @@ import com.threerings.cocktail.cher.dobj.DObjectManager;
 import com.threerings.cocktail.cher.server.net.AuthManager;
 import com.threerings.cocktail.cher.server.net.ConnectionManager;
 
+import com.threerings.cocktail.cher.server.test.TestObject;
+
 /**
  * The cher server provides a central point of access to the various
  * facilities that make up the cher layer of the system.
@@ -41,6 +43,9 @@ public class CherServer
             // create our distributed object manager
             omgr = new CherDObjectMgr();
 
+            // create an object for testing
+            omgr.createObject(TestObject.class, null, false);
+
         } catch (Exception e) {
             Log.warning("Unable to initialize server.");
             Log.logStackTrace(e);