[Zope3-checkins] CVS: Zope3/src/zope/app - context.txt:1.5

[Jim Fulton]

Update of /cvs-repository/Zope3/src/zope/app
In directory cvs.zope.org:/tmp/cvs-serv29292

Modified Files:
	context.txt 
Log Message:
Added some thoughts about the relationship between code and
it's access to implementation.


=== Zope3/src/zope/app/context.txt 1.4 => 1.5 ===
--- Zope3/src/zope/app/context.txt:1.4	Fri Jun  6 11:06:42 2003
+++ Zope3/src/zope/app/context.txt	Fri Jun  6 11:45:02 2003
@@ -209,6 +209,20 @@
     * Is there a helpful rule that's less general than "security
       proxies" always go on the outside?
 
+      + I think this has to do with how intrinsic something is.
+        
+        A descriptor from a class implementation should have full
+        access to the implementation.  If adapters could be registered
+        for classes, rather than interfaces, then the adapter could
+        have full access to the implementation.  An adapter from a
+        __conform__ should have access to the interface.
+
+        Adapters registered for an interface should only have access
+        to the interface.
+
+        This reveals, I think that class-based adapter registration is 
+        qualitatively different than interface-based registration.
+
   - What protects rename should be what protects setObject.
     We could declare that rename is to be protected with whatever protects the
     'setObject' operation on the proxied object.