[minion-cvs] Add comment arguing that, while we might eventually nee...

[nickm@seul.org (Nick Mathewson)]

Update of /home/minion/cvsroot/doc
In directory moria.mit.edu:/tmp/cvs-serv3885

Modified Files:
	minion-spec.tex 
Log Message:
Add comment arguing that, while we might eventually need to be able to
pull descriptors directly might eventually be useful, we should hold
off on speccing it till we find something that needs it.


Index: minion-spec.tex
===================================================================
RCS file: /home/minion/cvsroot/doc/minion-spec.tex,v
retrieving revision 1.73
retrieving revision 1.74
diff -u -d -r1.73 -r1.74
--- minion-spec.tex	12 Jan 2003 15:45:35 -0000	1.73
+++ minion-spec.tex	13 Jan 2003 06:46:18 -0000	1.74
@@ -99,6 +99,29 @@
 
  These are the reasons why I think it might be a good idea to have automatic 
  on request information from servers. -GD]
+[Hm.  You may have a point.  I'm still going to suggest that we do
+ not do this yet, for a few reasons.
+
+ First, we need a way for servers to publish their descriptors to
+ directory servers.  (Otherwise, a directory server couldn't learn
+ about new servers for the first time.)  In other words, a push
+ mechanism is needed no matter what.  On the other hand, directory
+ servers may or may not need a pull mechanism: we do not yet have a
+ design that requires this.  Let's not build it till we have a use
+ for it.
+
+ Second, it's a bit tricky to specify *which* descriptor a server
+ should return.  Today's?  Tomorrow's?  All the ones it knows about?
+
+ Third, (this is a variant of 'First') because client use of this
+ feature is prone to misuse, we should only provide it to clients
+ wrapped in some safe mechanism.  That safe mechanism has yet to be
+ specified.
+
+ Therefore, I'm going to suggest that we call this feature possibly
+ desirable... but that we should first design directories or whatever
+ other node discovery mechanisms *may* want this feature before we
+ decide that to implement the feature itself. -NM]
 
 \section{Message Format}