Add a game state log dumping facility that produces a (load)able sexpr-log.

[eow] / Notes

diff --git a/Notes b/Notes
index 84450c8edb39056ddf4b17683a12d6273c365aa2..72d09d698f766308a3997203aca522a09a8dba5c 100644 (file)
--- a/Notes
+++ b/Notes
@@ -1,3 +1,11 @@
+
+reproducible install
+ - dependencies
+ - install from clean state
+
+use sb-concurrency mailbox instead of own
+
+--------------------------------------------------------------------------------

 On COMET w/ hunchentoot: http://common-lisp.net/pipermail/tbnl-devel/2009-February/004620.html
 
 I have a working comet system using Hunchentoot.
 On COMET w/ hunchentoot: http://common-lisp.net/pipermail/tbnl-devel/2009-February/004620.html
 
 I have a working comet system using Hunchentoot.


@@ -26,3 +34,14 @@ available.
 (defun comet (fn &optional (session *working-session*))
   (setf (session-value 'comet-fn session) fn)
   (signal-semaphore (session-value 'comet-semaphore session)))
 (defun comet (fn &optional (session *working-session*))
   (setf (session-value 'comet-fn session) fn)
   (signal-semaphore (session-value 'comet-semaphore session)))

+
+--------------------------------------------------------------------------------
+
+Empire connection handling
+
+Maybe do something like cl-irc does with register/unregister handler. Might be
+even better combined with the modes system, provide an easy way to specify which
+event types a specific mode implementation is interested in. Register automatically
+on construction and deregister when leaving the mode.
+
+Using the object system like I do it right doesn't seem like a really good fit.