[Mailman-Developers] VERP_DELIVERY_INTERVAL not yet functional ?

Barry A. Warsaw barry@zope.com
Tue, 19 Feb 2002 23:30:05 -0500

>>>>> "fil" == fil  <fil@rezo.net> writes:

    >> The quick fix is to move the occasional VERP calculation into
    >> ToOutgoing.py, which is part of the munge-and-moderate
    >> pipeline, and thus will always have the up-to-date list data.

    fil> Is that really necessary? If it imposes some overhead, you
    fil> could use .... not (int(random() *
    fil> mm_cfg.VERP_DELIVERY_INTERVAL)): ...

That's an interesting idea, but moving the calculation to
ToOutgoing.py lets us do it a little more deterministically, with no
extra cost.

    >> A related, longer term fix is to make sure that OutgoingRunner
    >> occasionally reloads the list data, but that's a bit tricky
    >> because we can't count on reference counting (maybe we could
    >> use Python2.1's weakrefs?) and we don't yet have an API to
    >> invalidate the MailList's state.

I should mention that this change is really a "makes me feel better
about it" kind of change.  MM2.1 functionality shouldn't depend on
this, but someday, something will and it's better to fix it now than
to muddle over it all over again a year or so from now. :)  If it's
really a performance killer (and I think that it won't be bad given my
currently implementation), then we can remove it fairly easily.