From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: new feature request
Date: 21 Dec 1999 09:38:58 +1100 [thread overview]
Message-ID: <t4iiu1tfda5.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: Laura Conrad's message of "Thu, 16 Dec 1999 13:33:33 -0500"
>>>>> "Laura" == Laura Conrad <lconrad@gamesville.com> writes:
Laura> While we're discussing potential new features for the next
Laura> version: What about figuring out a way so that changing the
Laura> primary server doesn't destroy information about groups
Laura> that come from a secondary server? Or better yet, get rid
Laura> of the idea of a primary server altogether. Just have a
Laura> bunch of equal servers that store information about their
Laura> articles independantly.
At first, I didn't think much of this idea. I didn't think it was
worth the effort. However, I think there is one very good application
of having Gnus independent of the news server - laptops...
Consider this - you go to walk, plug in your laptop computer,
and tell it to read from the news server there.
You then take the computer home, plug it into your home network and/or
ISP, and tell it to use your news server here.
Now, it would be good if this could be supported, so that Gnus
can still keep track of read messages, etc, even though you are
constantly changing news servers.
Or another example: perhaps your main news server is off line, so you
need to use another, slower one, until the problem is fixed.
Even better would be if you could use such a feature if Gnus
Unplugged...
Implementation might be difficult though...
--
Brian May <bmay@csse.monash.edu.au>
next prev parent reply other threads:[~1999-12-20 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-16 18:33 Laura Conrad
1999-12-20 2:02 ` Brian May
1999-12-20 16:30 ` Alex Schroeder
1999-12-20 22:38 ` Brian May [this message]
1999-12-21 20:56 ` Kai Großjohann
2000-04-21 17:49 ` Lars Magne Ingebrigtsen
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=t4iiu1tfda5.fsf@silas-2.cc.monash.edu.au \
--to=bmay@csse.monash.edu.au \
/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).