Gnus development mailing list
 help / color / mirror / Atom feed
From: visigoth@naiad.fac.cs.cmu.edu
Subject: Re: IMAP revisited
Date: 09 Nov 1996 20:02:44 -0500	[thread overview]
Message-ID: <vpdg22iiwy3.fsf@naiad.fac.cs.cmu.edu> (raw)
In-Reply-To: David Moore's message of 09 Nov 1996 16:33:07 -0800

David Moore <dmoore@UCSD.EDU> writes:

> 	I must be missing something, since only the fetch commands to
> the backends have an article number provided by gnus.  Routines like
> BACKEND-request-accept-article are given a group and the body of the
> article and come up with their own number for it.
> 
> 	Or are you referring to the backend renumbering old articles
> when Gnus isn't looking?  That's a definite problem, certainly.

The IMAP model is that the server does all the message management
internally, including purges, reordering, whatever.  It keeps track of
flags on each message.  There -is- a UID (unique identifier)
associated with each message, but it's a little harder to work with
than just the sequence number.  <shrug>

There are a number of ways of dealing with this sort of thing.

As a note--I know of a couple of people (including myself) have looked
at doing IMAP for Gnus.  However, I just haven't had time to make any
significant progress, and I suspect the same is true of the other guy
I know who was looking at it.  (I'm sure he'll speak up if he's still
working on it.)

John.


  reply	other threads:[~1996-11-10  1:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-09 16:30 Steinar Bang
1996-11-09 21:31 ` Scott Blachowicz
1996-11-09 23:14   ` Sudish Joseph
1996-11-10  0:33     ` David Moore
1996-11-10  1:02       ` visigoth [this message]
1996-11-10 12:42         ` visigoth
1996-11-11 23:05     ` Paul Franklin
1996-11-14  8:52       ` Lars Magne Ingebrigtsen
1996-11-10 13:36 ` Kai Grossjohann
1996-11-10 13:40   ` Kai Grossjohann

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=vpdg22iiwy3.fsf@naiad.fac.cs.cmu.edu \
    --to=visigoth@naiad.fac.cs.cmu.edu \
    /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).