From 543f9774758035c5d9b4f1bc1e535f701292f5d4 Mon Sep 17 00:00:00 2001 From: Michael Bayne Date: Mon, 1 Oct 2001 22:11:53 +0000 Subject: [PATCH] Design notes. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@367 542714f4-19e9-0310-aa3c-eee0fc999fb1 --- docs/presents/notes.txt | 2 ++ docs/whirled/design.txt | 33 ++++++++++++++++++--------------- 2 files changed, 20 insertions(+), 15 deletions(-) diff --git a/docs/presents/notes.txt b/docs/presents/notes.txt index b8a0e6b82..6260a00f2 100644 --- a/docs/presents/notes.txt +++ b/docs/presents/notes.txt @@ -21,6 +21,8 @@ dispatched in unison. Build dobj source generator and have it add versions of all update methods that take a compound event to which to append the event rather than dispatching them directly. +Maybe make AuthResponseData a Streamable instead of a DObject. + * Server-side event concentrator The client objects will not subscribe directly, but will subscribe through the concentrator so that, at least, it can create a single diff --git a/docs/whirled/design.txt b/docs/whirled/design.txt index 4fbae4d4f..93d2a0de7 100644 --- a/docs/whirled/design.txt +++ b/docs/whirled/design.txt @@ -1,20 +1,5 @@ Whirled Design -*- mode: outline -*- -* Notes -Scene manager registers a timer when it becomes empty and flushes itself -from memory after timeout period. - -Client should avoid unsubscribing from scene objects straight away so that -it can avoid resubscribing if they bounce back and forth between scenes. - -We'll want the scenes to adhere to some sort of hierarchy so that we can -associate properties files with classes of scenes which will be used to -configure the scene managers when they are initialized. - -Add code to deal with receiving updated scenes from the server. - -Add code to flush scenes from the client scene manager cache. - * Overview Whirled builds on top of the Cocktail platform and provides a framework for building a virtual world made up of a node network of individual @@ -43,3 +28,21 @@ system at the time the client is delivered, and subsequent snapshots can be provided periodically to bring all clients into sync with the runtime scene database, from which they can then continue to mirror updates as needed. + +* Notes +Scene provider needs to do the right thing when a client requests an out +of date scene. Presently it doesn't handle sending the client the updated +scene data. + +Scene manager registers a timer when it becomes empty and flushes itself +from memory after timeout period. + +Client should avoid unsubscribing from scene objects straight away so that +it can avoid resubscribing if they bounce back and forth between scenes. + +We'll want the scenes to adhere to some sort of hierarchy so that we can +associate properties files with classes of scenes which will be used to +configure the scene managers when they are initialized. + +Add code to flush scenes from the client scene manager cache. +