← Back to team overview

openerp-expert-framework team mailing list archive

Re: [API, RFC] Generalized base class for messages

 

On Wednesday 26 May 2010, P. Christeas wrote:
> The thoughts, below, are surely draft, at a preliminary stage.

Already forgot 2 important points:
The direction of the message (ingoing/outgoing) should be in the _state_ and 
not a separate boolean flag. Reason is that there could be /external/ messages, 
which both originate and are delivered by an external agent, so these would 
have a special state.

Any more info than the plaintext body should be in attachments, one2many to 
ir.attachment . Even in the case of a html email, body should be the text, 
strictly, and the html part should be in attachments. It is essential to keep 
the body only having text in a semantic way, so that a message will be able to 
migrate to different medium  (eg. text-to-speech for phone, in an extreme 
case).



References