Skip to Content.
Sympa Menu

devel - Re: [sympa-developpers] Proposal on refactoring about message, spool and pipeline

Subject: Developers of Sympa

List archive

Chronological Thread  
  • From: Guillaume Rousse <address@concealed>
  • To: address@concealed
  • Subject: Re: [sympa-developpers] Proposal on refactoring about message, spool and pipeline
  • Date: Fri, 04 Jul 2014 13:41:36 +0200

Le 04/07/2014 06:20, IKEDA Soji a écrit :
My proposal was a bit illegible. In the figures,

[Pipeline::XXX]
|
|use
v
[Spool::XXX]
| |
|use |use
v v
context object
[List/Robot/Site] [Message/Task/etc.]

Dependency loop seems not to occur.

- Object packages (Message etc.) need not use'ing context package,
because latter have already been instantiated by Spool.
That's precisely this point I'm objecting, in favor of on-demand (delayed) context initialisation.

- Context packages (List etc.) need not use'ing object, spool nor
pipeline packages, because functions require them have been moved
to Pipeline package.

And it seems not possible that Pipeline never access to context
of each message: E.g. when a message is related to a list, pipeline
must access property (config parameter etc.) of that list.
That seems the more common usage, sure, but it is always true ? The bulk spool, for instance, seems to contains ready-to-send message, that just have to be feed to the SMTP engine. But I may be wrong, I really don't know this part of the code enough.
--
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




Archive powered by MHonArc 2.6.19+.

Top of Page