| | 101 | |
| | 102 | The prefs schema proposed here is not compatible |
| | 103 | with old-style prefs. |
| | 104 | We need to think about the following cases: |
| | 105 | |
| | 106 | * old client gets new-style prefs from a project |
| | 107 | * new client gets old-style prefs from a project |
| | 108 | * project with new server code gets old-style prefs from a client |
| | 109 | * project with old server code gets new-style prefs from a client |
| | 110 | |
| | 111 | The best approach I can think of is: |
| | 112 | |
| | 113 | * new prefs are stored in new XML elements |
| | 114 | * when new prefs are converted to XML, |
| | 115 | we generate old-style XML to the extent possible |
| | 116 | * the new client can parse both old- and new-style XML. |
| | 117 | If new-style is there, it ignore the old style. |