[Julien Anguenot]
...
I mean, this is an *after* commit hook after all. If one wants to change
persistent objects then one can use the beforeCommmitHook() (with
ordering support right ;) ) to launch it at the end just before the
actual commit.
I see, on my side, the afterCommitHook system
Hello Chris Withers,
Friday, September 23, 2005, 9:12:19 PM, you wrote:
CW Why not just use MaildropHost?
1. Because it is *nix only, it use os.fork(), using Thread.setDaemon(1) is
more friendly for me.
2. Because it takes all his options from Config file, not Zodb objects.
3. Because
Victor Safronovich wrote:
Hello Chris Withers,
Friday, September 23, 2005, 9:12:19 PM, you wrote:
CW Why not just use MaildropHost?
1. Because it is *nix only, it use os.fork(), using Thread.setDaemon(1) is
more friendly for me.
I KNOW Jens will accept good patches ;-)
2. Because it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Peters wrote:
[Victor Safronovich]
...
it should be better to add addAfterCommitHook to transaction
as in addBeforeCommitHook.
yup it could be really useful to trigger non transactionnal code from
there. We might use this in here
