From: Daniel Pittman <daniel@rimspace.net>
Cc: ding@gnus.org
Subject: Re: Offline mail and group cooperation
Date: Mon, 07 Oct 2002 12:30:45 +1000 [thread overview]
Message-ID: <87ofa7j7ze.fsf@enki.rimspace.net> (raw)
In-Reply-To: <873crj1ggd.fsf@crybaby.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sun, 06 Oct 2002 22:05:06 +0200")
On Sun, 06 Oct 2002, Kai Großjohann wrote:
> grossjoh@lothlorien.cs.uni-dortmund.de (Kai Großjohann) writes:
>
>> Another alternative might be to install a news server for our group,
>> and everybody installs leafnode on their laptop.
>
> I wonder how come that nobody commented on this alternative?
...because I didn't feel that I had very much to contribute. :)
> Is anyone out there using this?
Not in exactly the situation you talk about, but for similar things,
yes.
> How does it work? Does anyone have experience with this versus doing
> the shared folder thing via IMAP?
It works well, though leafnode tends to slow down as the local cache
size grows, because it simply dumps all articles for a single group in
the one directory. Thus, performance is directly related to the (usually
poor) filesystem directory search implementation.
> It would also be interesting to hear from people using an NNTP for
> group-local communication, without that extra offline stuff.
It's certainly very usable for this, what with being a many-to-many
communications medium. It tends to have better tools available for using
it than Shared IMAP, simply because it's been doing it longer.
> Maybe I can learn from it whether it is time-intensive to maintain
> your own NNTP server installation,
AFAIK, no, for a local server only. If you actually want to do news
peering and exchange with other news servers (not including
leafnode-style caching servers) then it's more involved.
OTOH I run a cache-only server myself, so I may not have the full
picture in my head.
Daniel
--
Reality is not as strong as perception. Perception all too often swallows
reality and spits it out in a new, unrecognizable form.
-- Maytee Aspuro
next prev parent reply other threads:[~2002-10-07 2:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 20:11 Kai Großjohann
2002-09-23 21:19 ` Alex Schroeder
2002-09-24 8:15 ` Kai Großjohann
2002-09-24 12:41 ` Clemens Fischer
2002-09-24 14:49 ` Kai Großjohann
2002-09-24 17:17 ` Alex Schroeder
2002-09-27 2:43 ` news
2002-09-27 10:24 ` Kai Großjohann
2002-09-27 17:05 ` Christoph Garbers
2002-09-27 17:59 ` François Pinard
2002-10-02 18:40 ` Scott A Crosby
2002-09-24 11:33 ` Simon Josefsson
2002-09-24 12:11 ` Kai Großjohann
2002-09-24 12:19 ` Kai Großjohann
2002-09-25 18:34 ` Björn Torkelsson
2002-09-26 8:14 ` Kai Großjohann
2002-09-26 8:44 ` dme
2002-09-26 14:40 ` Kai Großjohann
2002-09-26 16:11 ` Wes Hardaker
2002-09-26 16:59 ` Simon Josefsson
2002-09-26 17:11 ` Kai Großjohann
2002-09-26 17:28 ` dme
2002-10-17 19:54 ` Kai Großjohann
2002-10-17 20:15 ` Kai Großjohann
2002-10-20 19:53 ` Kai Großjohann
2002-09-24 11:55 ` Reiner Steib
2002-09-24 12:16 ` Kai Großjohann
2002-09-24 12:17 ` Christoph Garbers
2002-09-27 14:14 ` Frank Schmitt
2002-09-27 14:32 ` Kai Großjohann
2002-09-27 15:36 ` Frank Schmitt
2002-10-01 19:02 ` Paul Jarc
2002-10-06 20:05 ` Kai Großjohann
2002-10-07 2:30 ` Daniel Pittman [this message]
2002-10-07 23:25 ` Clemens Fischer
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=87ofa7j7ze.fsf@enki.rimspace.net \
--to=daniel@rimspace.net \
--cc=ding@gnus.org \
/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).