From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Writing changes back to sources
Date: Fri, 12 Mar 2010 10:22:22 -0500 [thread overview]
Message-ID: <1268407222-sup-8959@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <6c0c31751003072145r13f3bdd0m37f47c71995af06e@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 968 bytes --]
Excerpts from Scott Henson's message of Mon Mar 08 00:45:54 -0500 2010:
> To do the above I think we probably need standardize how messages
> are added and removed from sources. The maildir source has
> store_message and delete. I would suppose that we would need to
> implement something similar for the other sources (is mbox the only
> other one left?). Does this seem to be a good idea or do we want to
> continue having different ways of writing back to sources?
This is overall a good idea, I think. I haven't looked at this in
some time, so my memory may be off or the code changed in the interim,
but if you did something like this, you could like do away with
SentManager completely. Without the addition support of the mbox
store_message method, it would be a skeleton for default_set_source
(or whatever that method is)...at which point that functionality could
be handled differently.
Just a few (hopefully valid and useful) thoughts.
Thanks
-Ben
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-03-12 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 5:45 Scott Henson
2010-03-12 15:22 ` Ben Walton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1268407222-sup-8959@pinkfloyd.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox