106
edits
NSS Library Init: Difference between revisions
m
Fix (?) the Table of contents
(Update proposed names. Add questions of clarification) |
m (Fix (?) the Table of contents) |
||
| Line 1: | Line 1: | ||
= NSS Library Initialization = | |||
__FORCETOC__ | |||
== Problem == | |||
| Line 17: | Line 17: | ||
# Multiple libraries may be using NSS, multiplying the problems. | # Multiple libraries may be using NSS, multiplying the problems. | ||
How we initially intended to solve these problems | === How we initially intended to solve these problems === | ||
We intended to go to a single user/machine configuration for most applications and libraries, where all applications open the same set of databases for a particular user and machine. This configuration would not be in any one application's specific directory of application configuration files, but would be part of the system. One problem with this approach is that not all NSS applications run on systems which will have a 'system configured' NSS. In addition, there are still cases where the user may want to keep multiple different configurations for testing (Mozilla profiles for example). Finally, some applications only need read-only access to the NSS configuration, but other applications (like Firefox, or Thunderbird) need read-write access. This means if a read/only application initializes first, then a read/write application will not be able to update the database. (what?? --[[User:Nelsonb|MisterTLS]] 21:48, 1 September 2009 (UTC) ) | We intended to go to a single user/machine configuration for most applications and libraries, where all applications open the same set of databases for a particular user and machine. This configuration would not be in any one application's specific directory of application configuration files, but would be part of the system. One problem with this approach is that not all NSS applications run on systems which will have a 'system configured' NSS. In addition, there are still cases where the user may want to keep multiple different configurations for testing (Mozilla profiles for example). Finally, some applications only need read-only access to the NSS configuration, but other applications (like Firefox, or Thunderbird) need read-write access. This means if a read/only application initializes first, then a read/write application will not be able to update the database. (what?? --[[User:Nelsonb|MisterTLS]] 21:48, 1 September 2009 (UTC) ) | ||
Restrictions on any future solution | === Restrictions on any future solution === | ||
1) '''NSS must maintain binary compatibility.''' Applications should not become more broken as a result of linking with this new functionality. This means the existing shutdown should shutdown NSS in the same way that it has in the past. | 1) '''NSS must maintain binary compatibility.''' Applications should not become more broken as a result of linking with this new functionality. This means the existing shutdown should shutdown NSS in the same way that it has in the past. | ||