What do folks think about the ability to setup/teardown XPCOM components
(Gecko at large in more general embedding circumstances), multiple
times, in-proc. Obviously today you can init XPCOM, and shut it down
within a single process; _once_. There have been requests inside
Netscape/AOL to support the ability to do this multiple times. One
argument for such functionality is that you might be able to catch
structured C++ exceptions coming out of a Gecko thread in your Gecko
embedding app, shut down gecko, start it back up, and possibly continue
on without anything drastic happening (fat change, but, the possibility
exists). A counter to that is to "just fix the bugs."
Is there anyone else out there that would find this support useful; for
the reason stated, or others?
Netscape's trying to determine whether or not "restartable embedded
Gecko" should be a near term priority for us, and would appreciate feedback.
Jud
