Hello!
As soon as modules are involved there should be a blacklist for them
to not load some unwanted modules. Since the system administrator may
want to blacklist some modules system-wide, there is a reason to merge
system-wide blacklist with defined by user. I mean, there may be two
implementations of config parsing:
1) blacklist in user's config overwrites system config one therefore
system blacklist only relevant for initial value in user's config and
is always ignored later;
2) blacklist in user's config is added to system config one therefore
system blacklist is always taken into account.
What do you think is right way to implement the feature?
With best regards.
Andriy.
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxde-list
