Changes between Version 2 and Version 3 of CsMapRfc6
- Timestamp:
- 07/24/12 07:18:25 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CsMapRfc6
v2 v3 31 31 * Backing up customized definitions requires backing up all CSD files. 32 32 * Writing clean installer scripts is more difficult. 33 * File system privileges are more difficult to administer. 34 35 36 37 Users required to work with customized definitions have to be given write access to files which typically should be accessible by system administrators only. 33 * File system privileges are more difficult to administer. Users required to work with customized definitions have to be given write access to files which typically should be accessible by system administrators only. 38 34 39 35 40 36 Applications would benefit from the change proposed by this RFC in the following way: 41 * Sharing customized CS information becomes way easier. One would only have to share all or a subset of the *.CSD files from the user defined path. 42 No additional tool required that would extract / import customized definitions. 37 * Sharing customized CS information becomes way easier. One would only have to share all or a subset of the *.CSD files from the user defined path. No additional tool required that would extract / import customized definitions. 43 38 * Backing-up user-defined dictionaries becomes simpler. 44 39 * Writing clean installers (scripts) is less difficult. If customized definitions were separated from the system definitions, installer scripts could remove all previously installed files without having to include additional logic to handle modified *.CSD files.
