> - The role of the DeploymentManager is to find and return the > representations created by a DisseminationService.
If you're referring to DeploymentManager in the hlstorage POC, its purpose is to look up which ServiceDeployment object is associated with a given ServiceDefinition in the context of a given ContentModel. In Fedora, the ServiceDeployment object contains the information that is needed for binding an object to the specific implementation of the service. The problem is that the identity of the ServiceDeployment is considered to be a decision local to the repository, and can be changed at any time. Thus, when a service is invoked, Fedora knows the applicable CModel and ServiceDefinition, but does not know which ServiceDeployment it is supposed to use. In theory, several ServiceDeployments can exist within the same repository which could be applicable. To cope with this, the existing Fedora implementation of DOManager maintains a "model deployment map". Whenever a ServiceDeployment is ingested which claims to implement a particular ServiceDefinition for a particular ContentModel, it is indexed in this map DeploymentManager fulfills the role of maintaining the (CModel, SDef) -> SDep mapping, but allows designing implementations which are more appropriate to a distributed environment (e.g. use an external, shared service rather than a local in-memory hash table). -Aaron ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
