Replying to myself in case anyone is interested in the answer to my
problems...
Tim Hicks said:
Nope, I don't have a reference to a persistent object. I'm looking at the
code in smtpserver.SMTPServer and trying to figure out what I need to
adjust. As far as I can tell, the only point in
Paul Winkler said:
Ok, so I could simply drop the Zope.startup() line and things would be
fine (and quick), right?
I haven't tried it, but I think doing Zope.app() will try to
acquire a lock on the database and it is already locked by
the running Zope (or ZEO). So I don't think you can do
Paul Winkler said:
What I really want to be able to do from the server code is something
like::
root = magic_that_gets_me_zodb_root()
That magic is basically (from memory):
import Zope
Zope.startup()
root = Zope.app()
But note that starting up a zope is slow, so you don't
On Mon, Nov 08, 2004 at 11:22:13AM -, Tim Hicks wrote:
Paul Winkler said:
What I really want to be able to do from the server code is something
like::
root = magic_that_gets_me_zodb_root()
That magic is basically (from memory):
import Zope
Zope.startup()
In article [EMAIL PROTECTED] you write:
Hi,
I'm trying to figure out how to adjust Nikolay Kim's smtpserver code
http://cvs.sourceforge.net/viewcvs.py/collective/smtpserver/ so that
objects within the ZODB can affect the way that messages are received
(i.e. veto messages based on certain
Hi,
I'm trying to figure out how to adjust Nikolay Kim's smtpserver code
http://cvs.sourceforge.net/viewcvs.py/collective/smtpserver/ so that
objects within the ZODB can affect the way that messages are received
(i.e. veto messages based on certain criteria in the first instance).
My problem is
