On Aug 31, 2006, at 5:56 AM, Dmitry Dartz wrote:
Does this mean that single-profile is enabled by default?
It depends on what you're building.
Firefox browser?
(This is one thing I wish the build configurator did better -
made it clear
what the defaults are).
Check mozilla/config/autoconf.mk
I can certainly do that, however it's frustrating there's not an
easier/more straight-forward way of knowing what will be built if I
don't have anything in my .mozconfig file
Also, are you saying that with this disabled, there will be a static
library I should link against? Or will it produce a dynamic library
that ends up in the components folder? (I believe this was what
happened in Mozilla 1.7.5)
I think that neither are compiled while MOZ_SINGLE_PROFILE is 1 (in
case of 1.8.0.x).
But, I'm not sure if NS_PROFILE_CONTRACTID (profile manager) is
needed at all.
Firefox can live without it and why can't your application live?
Well, perhaps I'm misunderstanding how profile management is supposed
to work, but for my application (the software for LEGO Mindstorms
NXT, actually) we have multiple user profiles and they can log into
secure web sites. I want to keep the cookies separate so that users
can't access others' secure pages. The profile switch can happen in
the application without shutting down and restarting. I suppose I
can just have one profile and make it kill the cookies/session when
the user switch occurs, but I'd rather be able to persist the browser
state when they switch between users so that they're still logged in
when they switch back. This doesn't seem unreasonable to me, but
perhaps I'm missing something???
J
_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding
