Developers of Sympa

[Guillaume Rousse <address@concealed>]

Le 12/07/2013 15:01, IKEDA, Soji a écrit :
> On Fri, 12 Jul 2013 12:27:17 +0900
> IKEDA Soji <address@concealed> wrote:
> > On Thu, 11 Jul 2013 17:09:45 +0200
> > Guillaume Rousse <address@concealed> wrote:
> > > The second point is: do we really need different classes for storing
> > > different kind of content, and for how many different content types
> > > exactly ?
> >
> > I'll answer "Yes". Sympa uses several kind of content: Message,
> > bounce, message digest, task, and maybe request...
>
> There are following exactly different content types:
>
>    Message                 for "msg" and "bulk" spool,
>    Bounce message          for "bounce" spool,
>    Message to be moderated for "mod" spool,
>    Message to be archived  for "outgoing" spool.
-> message content

>    Topic tagging info.     for "topic" spool.
-> topic content

>    Accumulated posts       for "digest" spool.
-> message digest content (eventually just another kind of message)

>    Authentication token    for "auth" spool.
-> token content

>    Subscribe request       for "subscribe" spool,
>    Signoff request         for "signoff" spool.
-> request content

>    Task                    for "task" spool,
-> task content.

> That's all, I hope.
We already have classes for Message and Task, we'll need additional ones 
for Topic, Digests, Tokens, and Requests, implementing suitable interface.

And both spool implementations should be able to store/restore them.

Does it sound like a reasonable target ?
--
Guillaume Rousse
INRIA, Direction des systèmes d'information
Domaine de Voluceau
Rocquencourt - BP 105
78153 Le Chesnay
Tel: 01 39 63 58 31

Attachment: smime.p7s
Description: Signature cryptographique S/MIME