I think the idea was more along the lines of having the Mozilla organization host xpcom.org. It's a marketing/presentation change, not a change of ownership. Right now XPCOM is buried inside the Mozilla browser project and very few people are aware that it can be used as a standalone tool.  By giving XPCOM it's own identity it would have more of a chance to grow as a standalone platform. Something like xpcom.mozzila.org could work.
 
Another issue: why is there a browser build of XPCOM and a standalone build of XPCOM? Couldn't there be just a single XPCOM?  NSPR has a single version. There are only six XPCOM C files using XPCOM_STANDALONE. The differences look to be fairly small.
 
Has anyone from the NSPR group talked to the Apache APR group? Is there any hope of avoiding two portable runtime efforts? Apache has split APR off into a standalone project for 2.0.
 

Reply via email to