Changes between Version 9 and Version 10 of GROUP_APP_SERVER_RESOURCE_ACCESS_R0

Timestamp:

06/10/09 15:05:24 (16 years ago)

Author:

kyli

Comment:

--

GROUP_APP_SERVER_RESOURCE_ACCESS_R0

@@ -10 +10 @@
 == Task requirements ==
  * Decompose the server in appropriate modules with well-defined functionality (and do the refactoring needed):
-  * The core and the persistence should remain in separate modules.
   * Server persistence at this iteration is not a requirement. It can be fake (dumping everything to memory) for ease of implementation.
   * The Sophie2 Server should use the base resource model of Sophie2 (that includes book, users and groups at this iteration).
@@ -16 +15 @@
   * The modules should be well structured, with clear communication between each other. 
   * It would be good to create a draft diagram of the modules decomposition.
- * Add resource access support to the facade (it currently only provides access to user and group managers):
-  * Implement both the server-side and the client-side of the facade. The former will provide resource access to the web services and the web UI, while the latter will be used by the new palette created.
- * Provide ability for the web services to serialize resources in order to pass them to the client.
+ * Revise the currently implemented app_connectivity part (ability to establish a session), if it is not currently working, make it work with the new server model. It will be needed for resource listing. 
+ * Add resource access support for the server (it currently only provides access to user and group managers):
+  * Implement both the server-side and the client-side of the facade. This way the client will be able to connect to the server and access resources there.
  * Create a palette for listing server resources and make it work synchronously with the existing Connections palette (i.e. display the resources of the server we are connected to):
   * It should be in the Servers tab in the left flap.
   * At this iteration it should list all the resources on the server (users, groups, books). No resource list filtering is required.
   * It should support opening a book on a double-click (other actions will be implemented at a next iteration).
-  * It should be consistent with the Resources palette.
 
 == Task result ==