On Jun 14, 2008, at 5:27 PM, Atul Varma wrote:

>  I talked to Brendan on Thursday about this and I think that Mark is  
>  right:
>  Mozilla has no plans to abandon XPCOM outright, though by "putting  
>  it back
>  in its place" I get the impression that this means "using it as  
>  sparingly as
>  possible".  I believe this means that C++ components that only need  
>  to be
>  used by other C++ components will just be linked together rather  
>  than being
>  wrapped in XPCOM components, and JS code that just needs to be used  
>  by other
>  JS code will similarly be put in js-modules.  However, I could be  
>  wrong on
>  even that, so I'll post more updates here as I gain a better  
>  understanding
>  of the situation.


Thanks for the update & clarification.


>  On Mon, Jun 9, 2008 at 1:21 AM, Mark Hammond <mhammond@[...].au 
>  >
>  wrote:
> 
> > My understanding is that Mozilla isn't really "moving away" from  
> > xpcom,
> > just
> > putting it back in its place :)  I believe xpcom will still form  
> > the basis
> > of their public, stable/frozen APIs, although xpcom itself is  
> > likely to
> > need
> > to change for the mozilla2 platform.  The best reference I can find  
> > to
> > support this is from Brendan's blog of a couple of years ago:
> >
> > http://weblogs.mozillazine.org/roadmap/archives/2006/02/fresh_xpcom_thinking
> > .html<http://weblogs.mozillazine.org/roadmap/archives/2006/02/fresh_xpcom_thinking.html 
> > >,
> > and although it doesn't mention mozilla2, I believe it is relevant.
> >
> > Cheers,
> >
> > Mark
> >
> >> -----Original Message-----
> >> From: pyxpcom-bounces@[...].com [mailto:pyxpcom-
> >> bounces@[...].com] On Behalf Of Philip Semanchuk
> >> Sent: Monday, 9 June 2008 11:17 AM
> >> To: pyxpcom@[...].com
> >> Subject: Re: [pyxpcom] Firepy
> >>
> >>
> >> On Jun 8, 2008, at 12:05 PM, Atul Varma wrote:
> >>
> >>> Mozilla is also moving away from XPCOM,
> >>
> >>
> >> Hi Atul,
> >> Since I'm new to the XPCOM world I'm still trying to get my  
> >> bearings.
> >> I thought Mozilla was using *more* XPCOM, not moving away from it.  
> >> Can
> >> you enlighten me, please?
> >>
> >> Thanks
> >> Philip
> >> _______________________________________________
> >> pyxpcom mailing list
> >> pyxpcom@[...].com
> >> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
> >
> > _______________________________________________
> > pyxpcom mailing list
> > pyxpcom@[...].com
> > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
> >

_______________________________________________
pyxpcom mailing list
pyxpcom@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs