Re: Make gnus-agent another mail backend?

[Harry Putnam <reader@newsguy.com>]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
>
>>> Yes.  It would make the Agent's storage not correspond with the real
>>> server storage, meaning that we would have to implement ways of not
>>> letting expiry touch certain articles, etc.
>>
>> But isn't that already the case?  The stuff in an agentized group can
>> way outdate what is on the server.  Keeping up with that difference
>> was implemented way back about pgnus-[20-21].
>
> The real question is -- why on earth would you want to edit articles
> in the Agent?  Why wouldn't you just like to be able to edit any
> arbitrary article from any read-only backend?

What is the difference?  Would one have to do some kind of work to get
them into a state (in cache?), where this editing or other maillike
things could happen?  If this were automated it would be very similar
to what I was suggesting I think.

I didn't understand your argument about cache the first time around
though so maybe just not `getting it'.  Does cache offer the other
things that go with mail backends, like complex expiry?  Editing isn't
the only thing missing in agentized messages. It would be nice to be
able to target-expire them.  Especially if someone can think of a way
to base expiry on date AND score AND readedness.