"Simon P. Lucy" wrote:

> > But that may not be the case if XPCOM can be turned into a
> > system architecture instead of just used for application
> > plugins/extensions. MSCOM is powerful because classes which
> > are registered, are registered for the entire system. Wouldn't
> > it be nice to get this sort of component reuse at the entire
> > system level, not just for individual Mozilla type applications?
> 
> You'd really need out of process as well as in process going as
> well for a system component, which then implies data marshalling
> and the rest of it.  For a while I thought that was the intent
> and direction of XPCOM but I was wrong.

Why do you *need* that? You and I are using plenty of in-process system
"components" every days *today*, and look, nobody's dead yet because of
that. I'm not saying this is perfect, but that you'll live through it
without out-of-process...

On a lightly related subject, just about all COM source code that I saw
would die upon having an out-of-process component crash on them, anyway.
So much for out-of-process safety...

-- 
Pierre Phaneuf
http://www3.sympatico.ca/pphaneuf/

Reply via email to