From 9e7b10b31cabea8269fb538b90f10e2d5b072704 Mon Sep 17 00:00:00 2001 From: Michael Bayne Date: Tue, 2 Oct 2001 02:04:43 +0000 Subject: [PATCH] Mo' notes. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@373 542714f4-19e9-0310-aa3c-eee0fc999fb1 --- docs/parlor/design.txt | 7 +++++++ docs/whirled/design.txt | 4 ++++ 2 files changed, 11 insertions(+) diff --git a/docs/parlor/design.txt b/docs/parlor/design.txt index 41e5aa533..4b7f8557f 100644 --- a/docs/parlor/design.txt +++ b/docs/parlor/design.txt @@ -115,3 +115,10 @@ particular game and participating in the game on the client side. * Notes Where does the panel/view, controller stuff fit in? Should it be in its own package and used by the Parlor services or provided directly? + +Update ParlorManager to check access control related things before +accepting and delivering an invitation. + +How to prune stale invitations since invitations are not set up to be tied +to a location (in which case we could use occupant added/removed to +trigger invite cleanup)? diff --git a/docs/whirled/design.txt b/docs/whirled/design.txt index 93d2a0de7..3aae3a4eb 100644 --- a/docs/whirled/design.txt +++ b/docs/whirled/design.txt @@ -46,3 +46,7 @@ configure the scene managers when they are initialized. Add code to flush scenes from the client scene manager cache. +We need some mechanism for the scene registry to know which SceneManager +derived class to instantiate. Probably something like +Scene.getManagerClassName() which can be implemented by an application +when it creates its Scene implementation.