The mailing list for listmasters using Sympa

[Steve Shipway <address@concealed>]

Let me add my vote for a recursive trigger mechanism for list-type external datasource refreshes.

 

As you say, if listA includes listB, then a refresh of the external datasources on listA should trigger a refresh of external datasources on listB, probably in line with the distributionTTL defined for listB.

 

Already, there are many things that trigger a list membership refresh:

 

1.       By task_manager, when the TTL expires

2.       By distribute, when a new message comes in for the list and distribution_TTL has expired

3.       By wwsympa, when the list admin visits the subscribers review page and distribution_TTL has expired,

4.       By wwsympa, when the list admin clicks the ‘refresh external datasources’ button in the UI.

 

I think if you add a recursive refresh as you mention, the important thing would be to honour the distribution_TTL of the child lists in order to prevent excessive work (we have lots of LDAP external datasources and have to be careful about this)

 

Steve

 

---

Steve Shipway

ITS Unix Services Design Lead

University of Auckland, New Zealand

Floor 1, 58 Symonds Street, Auckland

Phone: +64 (0)9 3737599 ext 86487

DDI: +64 (0)9 924 6487

Mobile: +64 (0)21 753 189

Email: address@concealed

P Please consider the environment before printing this e-mail : 打印本邮件，将减少一棵树存活的机会

 

From: address@concealed [mailto:address@concealed] On Behalf Of David Verdin
Sent: Wednesday, 21 November 2012 4:17 a.m.
To: address@concealed
Subject: Re: [sympa-users] How to reload data sources per email interface?

 

Hi Paul,

Le 20/11/12 15:49, Paul Menzel a écrit :

Dear David,

Am Dienstag, den 20.11.2012, 15:31 +0100 schrieb David Verdin:

If you want scheduled updates, just change the ttl for your lists. The 

ttl is the config parameter that defined how long it takes between each 

synchronizations with the data sources.

thanks for the hint.

So judging from your response their is no callback(?) mechanism, that if

a subscriber is changed it notifies all “upper” lists it is included

into to refresh. That would be best, I guess.

Your guess is right...
Actually I think our top down mechanism would still work better.

Suppose you have three lists: A, B and C.
- list A includes list B
- list B includes list C
- lists C is synchronized with and LDAP.

When using the members list of list A, we could just trigger synchronization for any list included in list A.
This way, when accessing the list of users from list A, Sympa would do the following:

- require synchronization for list A
    |--> require synchronization for list B
        |--> require synchronization for list C
        |--> update list C with the content of LDAP directory
    |-->update list B with the updated content of list C
|--> update list A with the updated content of list B (itself updated with the updated content of list C)

This way, we would not have to bother updating any list which is included in another one (which would not be easy, as included lists do not "know" in which list they are included) and just make synchronizations when needed, and at the needed level (no need to update list A if we are only interrested in list B).

This will probably be quite easy to do, so I'll put it on our todo...

Cheers,

David

Thanks,

Paul

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature