[Grok-dev] Grokui and the security notifier

Souheil CHELFOUH trollfot at gmail.com
Fri Jan 29 07:20:37 EST 2010

Sorry guys to bother you again on that subject...
Making from the different panels some independant packages sounds like
a good move to me
What about splitting grokui.admin into : grokui.servercontrol and
grokui.appmanager ?
It makes senser to me, does it to you ? As we have now a common base,
it would be handy to plug what we want where we want it :)

2010/1/29 Souheil CHELFOUH <trollfot at gmail.com>:
> Nothing wrong about zope.processlifetime at all :)
> I'll use that and revert my changes, no worries at all :)
> 2010/1/29 Uli Fouquet <uli at gnufix.de>:
>> Hi there,
>> Martijn Faassen wrote:
>>> I think we used the security notifier once; I'm not sure. Why does it
>>> keep a zope.app.appsetup dependency alive?
>> It registers (well, registered) a persistent utility (the security
>> notifier) on IZopeDatabaseOpenedWithRootEvent.
>> As the security notifier has to store persistent data (for example the
>> enabled/disabled state), a regular global utiliy does not help here.
>> Is there a better way in general to store 'global' data?
>> Best regards,
>> --
>> Uli
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev at zope.org
>> https://mail.zope.org/mailman/listinfo/grok-dev

More information about the Grok-dev mailing list