X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=sfa%2Fgeneric%2Farchitecture.txt;h=66ac3c378d17446c977239179d0fbdf1f4239483;hb=3147e8e089dd44e40b852cc121483189807ffa9b;hp=cb81c8bd777c1f82045e761654641a6dc627b27f;hpb=f42832ac5338cb900a7d297cf6cdbe63bace6009;p=sfa.git

diff --git a/sfa/generic/architecture.txt b/sfa/generic/architecture.txt
index cb81c8bd..66ac3c37 100644
--- a/sfa/generic/architecture.txt
+++ b/sfa/generic/architecture.txt
@@ -3,7 +3,7 @@ We identify 3 layers in the server-side aspects:
 . api: this object reacts to an incoming SFA request
 
 . manager: this implements a given interface, either registry,
-aggregate, or slicemgr
+or aggregate
 
 . driver: this object is in charge of actually talking to the
 underlying testbed
@@ -19,9 +19,8 @@ configurable in a flavour (e.g. sfa.generic.pl.py)
 * a call to make_api will then create the 3 elements with the
   following layout:
 
-api.manager 
-manager.driver
-api.driver (for convenience)
+api.manager
+api.driver
 driver.api
 
 ------
@@ -37,5 +36,3 @@ with the arguments passed as arguments to the constructor
 
 ------
 more in sfa/generic/__init__.py
-
-