Re: (provide 'nnmaildir)

[prj@po.cwru.edu (Paul Jarc)]

I wrote:
> Still incomplete, though: no groups or expiration yet.
> <URL:http://multivac.cwru.edu/prj/nnmaildir.el>

Work on groups is progressing, along with fetching articles by
Message-ID.  Expiration will probably be next.

- Any advice on how to maintain (not necessarily persistent)
  per-server/per-group state between calls to backend functions?
  Maybe declare some server parameters, but advertise them as reserved
  for internal use?

- Any advice on what kind of information should be provided through
  server parameters, and what kind through package variables?

- Does Gnus give backends any way to save state between sessions in
  .newsrc.eld or the like?

- When Gnus calls my -open-server, it passes the server parameters
  from the select method set in .emacs, or the like (which I relay to
  nnoo-change-server).  When it calls my other functions, does Gnus
  ensure that the server to be operated on is current, by first
  calling -open-server?  Or am I to call -open-server myself, if
  necessary?  If I call it, I don't have the server parameters - will
  nnoo-change-server remember them from the first call with a given
  server name?  If not, how do I reestablish the proper values of
  server parameters?

- For moving articles between groups in nnmaildir, it makes sense to
  simply rename a message file and/or tweak some per-server persistent
  state data - in particular, *not* to copy a message from one file to
  another.  Can I work this into the -request-move-article and
  -request-accept-article interface, or is this too different of a
  framework?

- What's the likelihood of nnmaildir being officially incorporated
  into Gnus?

- I read on the list archive a while back that there might be some
  reworking of nnmail to be more flexible in dealing with mail
  backends (which might mean that nnmaildir could be a nnmail
  backend).  Is this still in the works?  Or maybe did it happen, and
  I missed it?


paul