Apart from this instance I've never heard a demand for such strict control, so I don't generally think it would be worthwhile. Making the call to change the status actually carry out the writes might be worth considering, perhaps it should be a method called on the context like .. container.setState(this, mail.GHOST) as I think we both agree that the de-coupling opens a "window of opportunity", to quote a popular military phrase.
> I don't know if we want to look at anything related to this for v3. We > would have to agree that mail *status* is always kept in a database, even > when mail content is stored in the file-system. I am amenable to > that as a > discussion. > > --- Noel > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
