The Open Anzo Project

Semantic Application Middleware

Ticket #121 (closed enhancement: fixed)

Opened 1 year ago

Last modified 1 year ago

Apply Service Container Arch to Client Components

Reported by: mroy Assigned to: mroy
Priority: critical Milestone: 3.0 milestone1
Component: openanzo Version: 3.0
Keywords: servicecontainer Cc:

Description

In order to reuse components within the system, it makes sense to be using the ServiceContainer on the client in order to manage the interaction between the client api and the server. This allows for the adding new services to the client in a consistent manor. The same components that are used to pass calls from the client apis to the server services can also be used to proxy service requests from one transport to another.

Change History

11/19/07 13:31:00 changed by mroy

(In [849]) re #121
reviewer: ben, jpbetz
Moved ServiceContainer components to the anzo-common module.
Applied ServiceContainer as the basis of client calls to server.
Created basic ontology for ServiceContainer configuration.
Basic loading of this configuration from rdf files.
IRepositoryService mode constants now in a RepositoryMode? enum.
Pure embedded mode not fully tested since authentication is stricter now and tests aren't written to test with this in mind.

11/19/07 13:33:23 changed by mroy

(In [850]) re #121
reviewer: ben, jpbetz
Moved ServiceContainer components to the anzo-common module.
Applied ServiceContainer as the basis of client calls to server.
Created basic ontology for ServiceContainer configuration.
Basic loading of this configuration from rdf files.
IRepositoryService mode constants now in a RepositoryMode? enum.
Pure embedded mode not fully tested since authentication is stricter now and tests aren't written to test with this in mind.

01/29/08 09:50:08 changed by mroy

  • status changed from new to closed.
  • resolution set to fixed.
Copyright © 2007 - 2008 OpenAnzo.org