Extract our permission policy into a separate class so that a system can more

easily make use of different permission policies in different circumstances
(one can imagine a hypothetical partner who has different access control
requirements, perhaps).


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

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

@@ -28,6 +28,7 @@ import com.threerings.util.Name;
 
 import com.threerings.presents.Log;
 import com.threerings.presents.data.ClientObject;
+import com.threerings.presents.data.PermissionPolicy;
 import com.threerings.presents.dobj.DObject;
 import com.threerings.presents.dobj.ObjectAccessException;
 
@@ -66,6 +67,14 @@ public class ClientResolver extends Invoker.Unit
         return new ClientObject();
     }
 
+    /**
+     * Creates a permission policy for use by our client.
+     */
+    public PermissionPolicy createPermissionPolicy ()
+    {
+        return new PermissionPolicy();
+    }
+
     /**
      * Called once our client object is registered with the distributed object system.
      */