Developers of Sympa

[Olivier Salaun - CRU <address@concealed>]

Sympa could check last update date when including a file but it does not
because it can have multiple include sources and Sympa does not keep
track of the source associated with each email. That's why it does the
big job every TTL seconds.

Hopefully it could be done since Sympa 3.4 that has an 'include2' feature
(described there : 
https://listes.cru.fr/wws/arc/sympa-dev/2002-08/msg00006.html)
that keeps track of the email<->include_source relationship and therefore 
could
allow a different TTL (and optimized behavior) for each include data_source.


John Douglass wrote:
> I had set the TTL on a list "6 seconds" on a 15,000 subscriber file 
> which totally bogged down my system ;) Hehhehehe.
>
> Perhaps the file include process could be improved upon by making the 
> following modification:
>
> TTL (when using file include) is the amount of time to check between 
> modifications. If the modified time is different than it's last check, 
> then update the list. Otherwise, leave it alone. I don't know how this 
> would be handled (because the last updated timestamp would have to be 
> held somewhere). Perhaps the .db file and the file included could be 
> constructed so that they both have the same timestamp (when the cache 
> (.db) is created).
>
> With included lists on DB, the TTL makes sense (because that query 
> really needs to be handled differently).
>
> Unsure if I'm beating a dead horse (I'm still on 3.3.5) but figured I'd 
> put this out there juuuust in case.


--
Olivier Salaun
Comite Reseau des Universites