Notes.

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

docs/presents/notes.txt

@@ -7,6 +7,15 @@ clientWillLogff becomes clientMayLogoff?
 
 Look into nbio waking up all sockets when any data comes in.
 
+(maybe) Allow piggybacking of object subscription onto service defined
+responses (like moveTo request).
+
+(maybe) Allow better server side control of subscription management (to
+ensure that clients don't remain subscribed to objects they should no
+longer be susbcribed to; like scenes they've departed from).
+
+Sort out support for server-side modifiable only fields to 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

docs/whirled/design.txt

@@ -1,5 +1,25 @@
 Whirled Design -*- mode: outline -*-
 
+* Notes
+Scenes map to places.
+
+Scene manager extends place manager, handles scene related stuff.
+
+Scene manager registers a timer when it becomes empty and flushes itself
+from memory after timeout period.
+
+Location manager is used to navigate between scenes on the client;
+location services will need extensions to support delivering scene version
+with moveTo request and serialized scene data with moveTo response
+(desirable to avoid extra server round-trips).
+
+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.
+
 * 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
@@ -28,23 +48,3 @@ 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
-Scenes map to places.
-
-Scene manager extends place manager, handles scene related stuff.
-
-Scene manager registers a timer when it becomes empty and flushes itself
-from memory after timeout period.
-
-Location manager is used to navigate between scenes on the client;
-location services will need extensions to support delivering scene version
-with moveTo request and serialized scene data with moveTo response
-(desirable to avoid extra server round-trips).
-
-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.