Changes between Version 1 and Version 2 of PrefsImpl


Ignore:
Timestamp:
Apr 25, 2007, 11:56:51 AM (17 years ago)
Author:
Nicolas
Comment:

Required manual changes to automatic conversion.

Legend:

Unmodified
Added
Removed
Modified

  • PrefsImpl

    v1 v2  
    11= Preferences implementation =
    22
    3 General preferences General preferences are represented by an XML element of the form:
     3== General preferences ==
     4
     5General preferences are represented by an XML element of the form:
    46{{{
    57<global_preferences>
    6      <source_project>http://setiathome.berkeley.edu/</source_project>
    7      <source_scheduler>http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi</source_scheduler>
     8    <source_project>http://setiathome.berkeley.edu/</source_project>
     9    <source_scheduler>http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi</source_scheduler>
    810    <mod_time>1140215730</mod_time>
    911    <run_if_user_active/>
    … …  
    3638</global_preferences>
    3739}}}
    38       The first set of preferences are the default; each set of venue-specific preferences is enclosed in a <venue> element. The optional <source_project> and <source_scheduler> elements indicate the source of the preferences.  On the client, the global prefs are stored in global_prefs.xml (present only if they've been obtained from a server).
     40
     41The first set of preferences are the default; each set of venue-specific preferences is enclosed in a <venue> element. The optional <source_project> and <source_scheduler> elements indicate the source of the preferences.  On the client, the global prefs are stored in global_prefs.xml (present only if they've been obtained from a server).
    3942
    4043A scheduler RPC request includes global_prefs.xml if it's present. If the request includes global prefs, the scheduler installs them in the DB if the DB copy is missing or older. If the DB copy is newer, it includes it in the reply. If the request has no prefs and they're present in the DB, they're included in the reply.
    … …  
    4245When handling a scheduler RPC reply that includes global prefs, the client writes them to global_prefs.xml, prepending the project and scheduler URLs is absent.
    4346
    44 Project preferences Project preferences are represented by an XML element of the form:
     47== Project preferences ==
     48
     49Project preferences are represented by an XML element of the form:
    4550{{{
    4651<project_preferences>
    … …  
    9499</project_preferences>
    95100}}}
    96        On the client, the project prefs are stored in a file account_XXX.xml, which has the additional elements  A scheduler RPC reply always includes project prefs. When handling a scheduler RPC reply, the client writes them to the account_X.xml file, prepending the master URL and authenticator.
    97101
     102On the client, the project prefs are stored in a file account_XXX.xml, which has the additional elements.
     103
     104A scheduler RPC reply always includes project prefs.
     105
     106When handling a scheduler RPC reply, the client writes them to the account_X.xml file, prepending the master URL and authenticator.