Combined notifications
The notifications sent by YACS are a powerful way to stay in touch with a complex server and with different threads of discussions. When someone posts a new comment, or a new file, in a thread or section you are monitoring, a message is generated to let you know as early as possible. This approach allows community member to check new items within seconds after their creations.
The drawback of this synchronous notifications is that, on large communities, or with very active threads, your mail box may rapidly be saturated by short mail messages sent by your server.
A more scalable way to advise people would be to queue notifications and to send only a couple of messages per day.
This supposes to implement some queueing mechanism for notifications in the database. This could be done by extending user profiles for example. Then, in the background, data accumulated there would be turned to actual e-mail messages. The delay between messages would be a global parameter set in the configuration panel for users.
The drawback of this synchronous notifications is that, on large communities, or with very active threads, your mail box may rapidly be saturated by short mail messages sent by your server.
A more scalable way to advise people would be to queue notifications and to send only a couple of messages per day.
This supposes to implement some queueing mechanism for notifications in the database. This could be done by extending user profiles for example. Then, in the background, data accumulated there would be turned to actual e-mail messages. The delay between messages would be a global parameter set in the configuration panel for users.
According to me, it's one more step to professional nature of our program
----- 
Comment YACS entend le droit de publication <- Un peu de visibilité à ce débat important pour YACS...
Yacs.Info : l'atelier ordinaire des innovations