summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGNU Hurd wiki engine <web-hurd@gnu.org>2007-08-20 09:10:43 +0000
committerGNU Hurd wiki engine <web-hurd@gnu.org>2007-08-20 09:10:43 +0000
commit6bf7b09cde5f9c30421e8367c59b8132ccdcf8ed (patch)
tree6e4211cdb6c25bc27a9963ecafb22bf7d412a481
parenteb511ef2ebf69de9662c5dea348f49729e70c849 (diff)
web commit by NealWalfield: Create.
-rw-r--r--namingcontext.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/namingcontext.mdwn b/namingcontext.mdwn
new file mode 100644
index 00000000..7e7b14d0
--- /dev/null
+++ b/namingcontext.mdwn
@@ -0,0 +1,14 @@
+Names are bindings to objects, however, to find an object
+given a name, the relation must be looked up in a
+naming context. A problem with using string as names is
+that it is very easy to lose track of the correct naming
+context. This is one of the problem with [[PassiveTranslators]]:
+a passive translator is a string. When the node is accessed
+on which the passive translator is set and there is no active
+translator, then an active translator is started using the
+passive translator setting. The active translator is started
+by the file system, not the program instance that set the
+passive translator. The passive translator settings are
+therefore resolved in the file system's naming context, which
+may be different from that of the program instance that set the
+passive translator setting. \ No newline at end of file