Jon Smirl wrote:
> I would also like to see XPCOM/NSPR as a standalone project that has Mozilla
> as it's biggest client. I use XPCOM (via XPConnect standalone) in a server
> environment that doesn't have Mozilla installed. By breaking the XPCOM/NSPR
> source out from Mozilla it would become much more valuable.
That seems like a very logical dividing line. Definitely bundle NSPR
along with XPCOM. I wonder what Wah-Ten thinks of this.
> Breaking out XPCOM would also make many more people aware of it's
> usefulness. How many of you know that you can call Java code from XPCOM (not
> using liveconnect)? How many can build the code? This works and I'm running it
> as I write this. Other people would probably add TCL, Python, etc to
> XPCOM world.
Python is there and Perl is probably close behind.
> Some Mozilla specific issues would also get resolved. For example,
> CreateInstance() is currently only supported from the thread that
> initialized XPCOM. For a general COM solution this has got to be fixed.
>
> I've also been wishing that NSPR and Apache APR would converge. Breaking out
> XPCOM/NSPR might allow this to happen.
>
> xpcom.org, xpcom.net, xpcom.com are registered to:
>
> Eusuf Ahmed
> 5227 Greendale
> Troy, MI 48098 US
> Phone: 734-355-1542
> Email: [EMAIL PROTECTED]
>
> No active systems appear to be attached to these names other than the
> register.com filler page.
I'm assuming that Netscape/AOL has trademarked XPCOM.
If not then perhaps they or some entity representing mozilla
should do so. Sending out "cease and decist" letters to cyber
squatters seems to be the fad these days.
Incidentally, |xp-com.org| appears to be available.
-rick
