In the design section of the plugins2 branch documentation, mention

wrapper functions as a component of a pluggable interface consumer
API.

git-svn-id: svn://anonsvn.mit.edu/krb5/branches/plugins2@24261 dc483132-0cff-0310-8789-dd5450dbe970

diff --git a/README.BRANCH b/README.BRANCH
index 61281cf074da84c0b7f71dfb5ad592bd89b5c94c..aad6f3f0a48cf339b733a5b7ec981ccbbfdec48a 100644 (file)
--- a/README.BRANCH
+++ b/README.BRANCH
@@ -46,6 +46,10 @@ API consists of:
   pluggable interfaces where the consumer wants to consult all
   available modules.
 
+* Wrapper functions for each plugin method.  Each wrapper function
+  should typically accept a krb5_context, a handle, and the specific
+  method arguments.
+
 3. Producer-facing dynamic module ABI
 
 A dynamic object can implement one or more plugin modules.  To