Changes between Version 1 and Version 2 of APP_CONNECTIVITY_REDESIGN

Timestamp:

07/27/09 16:35:35 (16 years ago)

Author:

kyli

Comment:

--

APP_CONNECTIVITY_REDESIGN

@@ -10 +10 @@
 This task is about redesigning the current connectivity model according to the new resource model and improving it so it reaches a stable beta phase.
 
+Since there are too many tasks about server and connectivity,they first need to be categorized, analyzed and scheduled. A clear vision for further procedure is needed - this task is about doing so.
+
+
 == Task requirements ==
-^(List the necessary requirements that the task must fulfill.)^
+
+Analyze the current status and what needs to be done for the following:
+ * The whole connectivity design must be revised (in this task) - what does is consist of, how does the client use the connectivity module, etc.
+ * Facade - since the resources are being redesigned, the facade needs to be changed. Real time collaboration support should be provided (sync methods).
+ * Connection list - the connection list in the client needs to be persisted, should provide manipulation ability, connections need to have clear statuses defined. 
+ * Server resource listing - the client needs to have a clear way of getting server resource lists (keeping in mind the security permissions). Also, needs to have filtering, searching, open/close support. This issue affects the server, too. 
+ * Client U.I. - there is currently a tab for the server stuff in the left flap, it must be re-designed and synchronized with our analysis men.
+ * Security - there is already some user/group model, but no logic is using it. Analyze / design the base security model.
 
 == Task result ==
-^(List the end product of the task (for example "Source code", "Wiki page", etc.))^
+ * In the design - design documentation for every connectivity aspect discussed above. Design diagrams are needed, auto tests are obligatory.
+ * In the implementation - Achievable schedule of what will be accomplished in what time, considering connectivity. The common design must be implemented as a basis for the next tasks. The tasks which will be implemented should be grouped and (optionally) analyzed. 
 
 == Implementation idea ==
-^(Provide some rough implementation idea(s).)^
-
+ * The base.connectivity module currently does not maintain the list of the available connections - they are kept in the corresponding palette. Consider this behavior. 
+ * There is a design draft for the new resource facade after the resource redesign - [http://pastebin.asteasolutions.net/f444cc8f1]. Another idea is that the client implementation of the facade is used by the server resource accesses, and the server-side implementation uses the server resource accesses.
+ * Connection listing should mainly use the server resource access, so it must be synchronized with other teams' work.
+ 
 == Related ==
 ^(Add links to related tasks that could be useful or helpful.)^