Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Backend writing
Date: Fri, 03 Aug 2001 15:39:59 -0400	[thread overview]
Message-ID: <m33d79c4pm.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <suse-7.0-professional.m2hevpaulk.fsf@tcob1.net> (Sean Rima's message of "Fri, 03 Aug 2001 19:04:07 +0100")

Sean Rima <sean@**Delete**.tcob1.net> writes:
> What I seek is a detailed FAQ on writing backends. Anyone know where I
> could get one, part from the info files.

If there's anything you need to know that isn't in the manual, it
probably ought to be added.  Ask questions here so the maintainers
know what to add.

One thing that I would have liked to find there, but didn't, is what
conditions article numbers must satisfy.  Numbers of new articles must
be greater than all existing numbers.  They should probably start from
1; they must not be zero or negative.  As long as you start from 1 and
increment by 1, don't worry about what happens when you reach 2^28
(the largest integer Elisp can handle); no one else does, and it
hasn't been a problem yet.  Unless you do something unusual like
nnmaildir does, an article must keep the same number for its entire
lifetime - once assigned to an article, a number cannot be reassigned
to another article.

nnfoo-request-scan is described as optional - Gnus can get by without
it - but it'll make your life easier if you implement it.  That was my
experience, anyway.

A good way too see what precise format things must be in in
nntp-server-buffer is to look at the contents of that buffer
(" *nntpd*") while using an existing backend.


paul


  parent reply	other threads:[~2001-08-03 19:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-03 18:04 Sean Rima
2001-08-03 19:24 ` Kai Großjohann
2001-08-03 19:39 ` Paul Jarc [this message]
2001-08-03 20:57   ` Kai Großjohann
2001-08-03 21:36     ` Paul Jarc
2001-08-03 22:16       ` Kai Großjohann
2001-08-03 21:44     ` Simon Josefsson
2001-08-03 22:07       ` Kai Großjohann
2001-08-03 23:35         ` Simon Josefsson
2001-08-03 23:46           ` Paul Jarc
2001-08-04  0:11             ` Simon Josefsson
2001-08-04  0:20               ` Paul Jarc
2001-08-04  0:41                 ` Simon Josefsson
2001-08-04  0:57                   ` Paul Jarc
2001-08-04 12:36                     ` Simon Josefsson
2001-08-05  8:27                       ` Paul Jarc
2001-08-03 23:57           ` Paul Jarc
2001-08-04  0:12             ` Simon Josefsson
2001-08-04  0:21               ` Paul Jarc
2001-08-04 11:46           ` Kai Großjohann

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=m33d79c4pm.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.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).