Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kevin.greiner@vignette.com>
Subject: Re: Cache and agent ?
Date: Thu, 23 Sep 2004 23:08:47 -0500	[thread overview]
Message-ID: <ullf0ux4g.fsf@vignette.com> (raw)
In-Reply-To: <plop87u0tqw9uj.fsf@gnu-rox.org>

Xavier Maillard <zedek@gnu-rox.org> writes:

> On 21 sep 2004, Kevin Greiner wrote:
>
>> Xavier Maillard <zedek@gnu-rox.org> writes:
>> 
>> > Hello,
>> > 
>> > Is it non-sense to have articles cached and have it
>> > downloaded by the agent at the same time ?
>> > 
>> > How is it processed internally then ?
>> > 
>> > (I have a group full of downloaded *and* cached articles due
>> > to a problem on my side).
>> 
>> The agent and cache are completely independent. So you have two
>> copies of each article on your harddisk.
>
> So, my next question is simply: is this situation safe ? Err,
> from where Gnus fetch the article then ? (cache ?, agent ?,
> randomly ?).

It's deterministic; it should prefer the cache.  The actual logic is
recursive and, at times, obscure so some functions may check the agent
first.

  
>> In anticipation of the next question, the agent and cache were
>> designed this way deliberately.
>
> No problem with how this was done ;) just a question. Do you
> think caching adn agentizing in the same time, a recommended/safe
> practice ? Oh, and given the fact I am caching ticked/dormant and
> even unread articles, can I safely enable agent expiration on my
> groups ? If I understand correctly, caching prevent me from a
> server expiration and adjusting in this case 2 or 3 more
> variables I can still keep a copy of some articles locally (no
> expiration can apply).

Very good, you found the primary justification for keeping the cache
and agent separate.  Agent expiration only applies to the agent's
folders so your cached articles can NOT be expired.  Note: An article
that is both cached and agentized may, by expiration, end up only
cached.

I'm not sure about your 'server expiration' comment.  My interest has
largely been the agent.

Kevin



      reply	other threads:[~2004-09-24  4:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-18 23:32 Xavier Maillard
2004-09-21  5:45 ` Kevin Greiner
2004-09-22 16:24   ` Xavier Maillard
2004-09-24  4:08     ` Kevin Greiner [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=ullf0ux4g.fsf@vignette.com \
    --to=kevin.greiner@vignette.com \
    /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;
as well as URLs for NNTP newsgroup(s).