439
edits
Talk:NSS Library Init: Difference between revisions
Jump to navigation
Jump to search
→NSS_Init() semantics change after a call to NSS_LibraryInit() ??
| Line 30: | Line 30: | ||
subsequent calls to the older traditional NSS_Init functions change their behavior. I think this violates the principle of least astonishment. Well, that's an oversimplification, but I need to commit this now, and will expand on it later. This is probably the BIG issue! | subsequent calls to the older traditional NSS_Init functions change their behavior. I think this violates the principle of least astonishment. Well, that's an oversimplification, but I need to commit this now, and will expand on it later. This is probably the BIG issue! | ||
It would be if that was what it really said. | > It would be if that was what it really said. | ||
NSS_Init is still idempotent. What changes is now NSS_Init is called, but NSS has already been initialized with NSS_ContextInit(). The first of these NSS_Init calls will do the same tap-dance that any NSS_ContextInit does. Subsequent NSS_Init calls will continue to act as they do today. I've changed the document working to make this more clear. | > NSS_Init is still idempotent. What changes is now NSS_Init is called, but NSS has already been initialized with NSS_ContextInit(). The first of these NSS_Init calls will do the same tap-dance that any NSS_ContextInit does. Subsequent NSS_Init calls will continue to act as they do today. I've changed the document working to make this more clear. | ||