From: Josh Huber <huber+news@alum.wpi.edu>
Subject: Re: No Gnus feature request: simpler file structure for synching
Date: Wed, 07 Jan 2004 14:17:52 -0500 [thread overview]
Message-ID: <877k03r2jj.fsf@amalthea.paradoxical.net> (raw)
In-Reply-To: <87isjn1whw.fsf@emptyhost.emptydomain.de>
Kai Grossjohann <kai@emptydomain.de> writes:
> Then you'd sync nothing for the nnimap part (all state is kept on
> the server, except for the list of groups you subscribe to -- but
> that doesn't change so often), and the single file for the nntp
> part.
Doesn't IMAP also support storing subscription information on the
server? Does Gnus use this? I guess not, since the subscribed groups
in Gnus were not subscribed via Squirrelmail. (and vice-versa)
I wonder if we could use IMSP to store ALL gnus configuration? now,
wouldn't that be cool? Does it have enough features?
http://asg.web.cmu.edu/cyrus/rfc/imsp.html
Then, no syncing would be needed -- all information would be stored on
the IMAP/IMSP server.
--
Josh Huber
next prev parent reply other threads:[~2004-01-07 19:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 0:24 No Gnus feature request: simpler file structure for synching between two machines John Owens
2004-01-07 7:22 ` No Gnus feature request: simpler file structure for synching Matt Armstrong
2004-01-07 8:27 ` Steve Youngs
2004-01-07 12:44 ` Kai Grossjohann
2004-01-07 14:28 ` Reiner Steib
2004-01-07 14:59 ` Kai Grossjohann
2004-01-07 17:42 ` nnir problems (was: No Gnus feature request: simpler file structure for synching) Reiner Steib
2004-01-07 16:20 ` No Gnus feature request: simpler file structure for synching Steven E. Harris
2004-01-08 22:23 ` Reiner Steib
2004-01-08 22:51 ` Steven E. Harris
2004-01-08 22:58 ` Paul Jarc
2004-01-07 17:07 ` John Owens
2004-01-07 17:47 ` Kai Grossjohann
2004-01-07 19:17 ` Josh Huber [this message]
2004-01-07 21:32 ` Simon Josefsson
2004-01-08 19:49 ` Steinar Bang
2004-01-11 21:49 ` Kai Grossjohann
2004-01-12 22:15 ` Steinar Bang
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=877k03r2jj.fsf@amalthea.paradoxical.net \
--to=huber+news@alum.wpi.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).