Changes between Version 8 and Version 9 of APP_CONNECTIVITY_REDESIGN

Timestamp:

07/30/09 12:00:48 (16 years ago)

Author:

kyli

Comment:

--

APP_CONNECTIVITY_REDESIGN

@@ -39 +39 @@
 
 = Design =
+ * The facade will be changed with the one from the draft (see implementation idea) and it will need sync methods (probably syntToMaster and syncFromSlave). The majority of its methods will return objects of type Response - they contain a result object, response status and eventually status message. This way, if the server cannot serve the client request, it can give some information about the type of the problem.
+ * ServerConnection should not be part of the model, but the model should know about pairs (server, user). So, we introduce a new class - Account. It consists of String serverUrl, String userName, String password, String accountName, Boolean autoConnect and Boolean savePassword - the most probable candidates for persisting before client shutdown. Accounts must not know about connections, but every connection should know the account is has come from. So, the new !ServerConnection class has !ConnectionStatus status, String sessionId, Account account and a private instance of a facade. Furthermore, the !ServerConnection has all the methods that the facade interface has, but with one difference: The facade methods return object of type Response<T> and need sessionId, the connection methods return object of type T and do not need sessionId(since the connection has its own id). This way, the connection can read the contents of a response and eventually react to their status(throw error messages, etc). 
+ * There will be an AccountManager which maintains list of available server accounts. For every acocunt, it will create a corresponding server connection. The connection will not be active before calling its "connect" method. Note that connect is not the same as login - connect just finds an appropriate facade implementation, instantiates it and gets a sessionId from the server. The login then can authorize the user, but some functionalities do not require the user to be authorized. Communicating with the server without logging in will be treated as annonymous connection.
+
  * ServerConnection:
   * Represents a connection to a server, instantiated from a given Account.