Changes between Version 11 and Version 12 of AccountManagement

Timestamp:

Nov 26, 2010, 8:24:48 PM (13 years ago)

Author:

davea

Comment:

--

AccountManagement

@@ -4 +4 @@
 To create an account with BOINC projects, a participant must:
 
-    * Locate BOINC project web sites, e.g. using Google.
-    * Read the web sites, and decide which to join;
-    * Download and install the BOINC client software. 
+ * Locate BOINC project web sites, e.g. using Google.
+ * Read the web sites, and decide which to join;
+ * Download and install the BOINC client software. 
 
 and then for each selected project:
 
-    * Go through the Attach to Project wizard. 
+ * Go through the Attach to Project wizard. 
 
 If the participant chooses N projects, there are N web sites to visit and N Wizards to complete.
@@ -20 +20 @@
 A typical account management system is implemented as a web site. The participant experience is:
 
-    * Visit the account manager site, set up a 'meta-account' (name, email, password),
-          browse a list of projects, and click checkboxes to select projects.
-    * Download and install the BOINC client software from the account manager.
-    * Enter the meta-account name and password in a BOINC client dialog. 
+ * Visit the account manager site, set up a 'meta-account' (name, email, password),
+ browse a list of projects, and click checkboxes to select projects.
+ * Download and install the BOINC client software from the account manager.
+ * Enter the meta-account name and password in a BOINC client dialog. 
 
 This requires many fewer interactions than the manual approach.
@@ -33 +33 @@
 [[Image(http://boinc.berkeley.edu/acct_mgt2.png)]]
 
-   1. The participant sets up his meta-account and selects projects.
-   2. The account manager issues a create account RPC to each selected project.
-   3. the participant downloads and installs the BOINC client software from the account manager.
-      The install package includes a file (specific to the account manager) containing the URL of the account manager.
-   4. The BOINC client runs, and asks the participant to enter the name and password of his meta-account.
-   5. The BOINC client does an RPC to the account manager, obtaining a list of accounts.
-      It then attaches to these accounts and proceeds. 
+ 1. The participant sets up his meta-account and selects projects.
+ 2. The account manager issues a create account RPC to each selected project.
+ 3. the participant downloads and installs the BOINC client software from the account manager.
+ The install package includes a file (specific to the account manager) containing the URL of the account manager.
+ 4. The BOINC client runs, and asks the participant to enter the name and password of his meta-account.
+ 5. The BOINC client does an RPC to the account manager, obtaining a list of accounts.
+ It then attaches to these accounts and proceeds. 
 
 There are [WebRpc web RPCs] to create, look up, and modify accounts.
@@ -87 +87 @@
 
  URL::
-        BASE_URL/rpc.php, where BASE_URL is the URL of the account manager web site.
+     BASE_URL/rpc.php, where BASE_URL is the URL of the account manager web site.
  input::
 {{{
@@ -98 +98 @@
     <client_version>5.3.2</client_version>
     <run_mode>auto</run_mode>
-        <not_started_dur>X</not_started_dur>
-        <in_progress_dur>X</in_progress_dur>
+    <not_started_dur>X</not_started_dur>
+    <in_progress_dur>X</in_progress_dur>
     <global_preferences>
         <source_project>http://a.b.c</source_project>
@@ -113 +113 @@
        <hostid>NNN</hostid>
        [ <attached_via_acct_mgr/> ]
-           [ <suspended_via_gui/> ]
-           [ <dont_request_more_work/> ]
-           [ <detach_when_done/> ]
-           [ <ended/> ]
+       [ <suspended_via_gui/> ]
+       [ <dont_request_more_work/> ]
+       [ <detach_when_done/> ]
+       [ <ended/> ]
     </project>
     [ ... other projects ]
@@ -189 +189 @@
 }}}
  action::
-        Returns a list of the accounts associated with this meta-account. The arguments are:
+    Returns a list of the accounts associated with this meta-account. The arguments are:
 
  * '''password_hash''': the account password, hashed as MD5(password_lowercase(name)). 
@@ -219 +219 @@
   * '''dont_request_more_work''': whether work fetch is suspended for this project
   * '''detach_when_done''': whether project is set to be detached when done
-
-In addition, a list of projects and their suspended flags is included.
 
 The return values are:
@@ -286 +284 @@
 A suggested method of maintaining a user's hosts is as follows:
 
-    * Maintain a host table with columns
-          * user ID
-          * project ID
-          * DBID
-          * CPID 
-    * On each account manager RPC, for each reported project,
-          look up (user ID, project ID, DBID) in the host table (where 'DBID' is the one passed in the RPC request).
-          If no record is found, create one. In any case, update the record with the CPID from the RPC request.
-    * To show the user a list of their hosts, with current per-project credit:
-          do a show_user.php RPC to each project to get a list of hosts.
-          Update the corresponding records in the host table, based on the DBIDs returned by show_user.php.
-          Delete any host table entries for this user/project that don't appear in the RPC reply.
-          Ignore the CPIDs returned by the show_user RPC (they may not be consistent).
-          Then do a query on the host table, grouping by CPID. 
+ * Maintain a host table with columns
+  * user ID
+  * project ID
+  * DBID
+  * CPID 
+ * On each account manager RPC, for each reported project,
+ look up (user ID, project ID, DBID) in the host table (where 'DBID' is the one passed in the RPC request).
+ If no record is found, create one. In any case, update the record with the CPID from the RPC request.
+ * To show the user a list of their hosts, with current per-project credit:
+ do a show_user.php RPC to each project to get a list of hosts.
+ Update the corresponding records in the host table, based on the DBIDs returned by show_user.php.
+ Delete any host table entries for this user/project that don't appear in the RPC reply.
+ Ignore the CPIDs returned by the show_user RPC (they may not be consistent).
+ Then do a query on the host table, grouping by CPID. 
 
 == Client configuration files ==
@@ -310 +308 @@
 It is typically included in an installer package.
 Its format is:
+
 {{{
 <acct_mgr>