Version 5 (modified by meddle, 16 years ago) (diff) |
---|
Analysis
Overview
The Sophie 2 Server Facade layer provides interface which is the same on both the server and the client sides for manipulating the resources on the server. The Facade layer accesses the Server core logic.
Task requirements
- The basic object model of the Facade should be build. The Facade should be extendable.
- The part of the Facade used for security purposes should be made functional.
- The current code should be refactored to use the Facade layer.
Task result
- Basic interfaces representing the Facade skeleton.
- Implementations of these interfaces for the security logic that is built at the moment.
- The current code that uses the core logic refactored to use the security implementations of the Facade interfaces.
Implementation idea
- Build Facade interface and interfaces for all the current security logics (users, groups). The Facade interface implementations will provide implementations of these logics.
- Implement the security facade logic for the mock server and the server itself. The login method should return session id (UUID) instead of user and the security part of the facade will keep a map in itself with sessionId -> user values.
- Refactor the mock server, the web interface and the web services to use the newly coded security facade.
Related
S2S_DEPLOY_TECHNOLOGIES_R0
S2S_CORE_SECURITY_R0
S2S_WEB_USER_RELATED_R0
S2S_WEB_SERVICES_R0
S2S_WEB_COMMONS_R1
S2S_CORE_MOCK_SERVER_R0
S2S_FACADE_RESOURCE_ACCESS_R0
S2S_FACADE_RESOURCE_CHANGES_R0
S2S_FACADE_LARGE_RESOURCE_ACCESS_R0
S2S_FACADE_META_ACCESS_R0
How to demo
Show the new object model, run the test and demonstrate that the refacored mock server, web interface and web services are running like before.
Design
Implementation
(Implementation results should be described and linked here (from the wiki or the repository))
Testing
Comments
(Write comments for this or later revisions here.)