> Is it because it uses an existing Mozilla browser DB connection?
I have seen my competition making "plug-in" (an app that sign/verify data using Mozilla cert store) for Mozilla browser using JSS and Java:
http://www.mozilla.org/projects/security/pki/jss/
I wonder why JSS does work properly with Mozilla cert store?
If/when JSS runs inside the browser, it shares the browser's view of the DBs. If/when JSS runs in a process separate from the browser, then it is subject to the same concurrent access limitations that I wrote about earlier.
> Is it possible to make Mozilla plug-in that would use Mozilla existing DB
connection, but to be also available (able to run) when Mozilla is closed?
Imagine having a very small process that is a DB server for the cert and key DBs. Imagine that mozilla doesn't access the DB directly, in process, but talks to this DB server via IPC for all DB accesses. Then any number of processes could act as simultaneous clients to this server. This could work for Thunderbird and FireFox. It would not be necessary for any particular client to run while the server is running. The server could go away when the last client drops its connection. Clients could start the server when they need one. It's just a small matter of programming. :)
Thank you very much for your help.
_______________________________________________ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
