Hanno Hecker wrote:
Hi,
this patch sets a way to disable any loaded plugin(s) for the current
client. I'm not going to commit this before Ask released 0.43. Matt
(and others with high traffic) should be ok with the one more line
next unless $code->{run};
per hook.
The plugins_loaded() should be in to Qpsmtpd.pm. Any other comments on
this?
I'm currently looking for a way to have plugins loaded but disabled (so
some other plugin can enable it later). Loading plugins on connect or
later at runtime would probably be possible, but too slow...
(Note to self: write docs before any commit)
I'm not sure this is the right way to do this. Surely you want something
in the transaction object that can "skip" plugins at run time? Yours
seems like a rather heavy hammer, which can be influenced in a very
bizarre cross connection manner.
Matt.
