Developers of Sympa

[John Douglass <address@concealed>]

From my reading do these statements:
---------------

Updates of the cache are performed by the task_manager

* Advantages

       + lower memory usage :
       Sympa processes used to use lots of memory when managing
       big (>200 000) 'include' types of lists. The list of 
       subscribers is now stored in the database.

       + updating the cache :
       Cache update is now performed by the task manager. It used to
       be performed by sympa.pl and wwsympa.fcgi.

* Task manager 

New 'sync_include' list task : 
Only one model (ttl) is available. TM checks if the list is in 'include2' mode and runs the sync_include. The syn_include()
does an in-memory comparison of already cache users list and included users 
list ; subscriber_table is then updated. List::delete_user() and 
List::add_user() have been optimized to make sync_include() faster. A new 
task is created based on 'ttl' list parameter.
-------------------

Does this now mean that future versions can "update" from an included source 
(such as LDAP or MySQL) at a predetermined time? When using LDAP based includes, if the 
ttl expires, it seems the NEXT user could experience a timeout if it's a particularly 
long period of time (hence why I upped the timeout value in Apache).

Also, are there plans to include within a list definition an "EXPIRES" date? 
We have some semester based lists that it would be nice to have close automatically 
(but not purge) based upon a supplied date.

- John Douglass, Georgia Institute of Technology