From: Dave Abrahams <dave@boostpro.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Why gnus-sync?
Date: Wed, 24 Oct 2012 16:13:10 -0400 [thread overview]
Message-ID: <m2hapjtyqx.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <87zk3bzmon.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 24 Oct 2012 15:37:12 -0400")
on Wed Oct 24 2012, Ted Zlatanov <tzz-AT-lifelogs.com> wrote:
> On Wed, 24 Oct 2012 12:56:51 -0400 Dave Abrahams <dave@boostpro.com> wrote:
>
> DA> I was just thinking about using gnus-sync to synchronize my newsgroups
> DA> across computers, but then I realized (I think) that I could just keep
> DA> my .newsrc* in a Dropbox or some such. Is there any advantage to
> DA> gnus-sync over an arrangement like that?
>
> The LeSync (CouchDB) backend is a bit better about synchronizing: it
> won't overwrite newer data when you `s'ave the marks, and it has a
> timestamped ID for every group. So you can read some groups and only
> save those, not the whole file.
So... it'll work if I read mail on multiple machines at the same
time? Is that the idea?
I guess I'd like to request a test DB, e.g.
http://lesync.info:5984/dabrahams
Thanks,
--
Dave Abrahams
BoostPro Computing Software Development Training
http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
next prev parent reply other threads:[~2012-10-24 20:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 16:56 Dave Abrahams
2012-10-24 19:37 ` Ted Zlatanov
2012-10-24 20:13 ` Dave Abrahams [this message]
2012-10-24 21:43 ` Ted Zlatanov
2012-10-24 22:41 ` Dave Abrahams
2012-10-26 12:06 ` Ted Zlatanov
2012-10-26 16:25 ` Dave Abrahams
2012-10-26 16:26 ` Ted Zlatanov
2012-10-26 16:28 ` Dave Abrahams
2012-10-26 16:32 ` Ted Zlatanov
2012-10-27 14:30 ` Steinar Bang
2012-10-27 14:48 ` Steinar Bang
2012-12-02 16:18 ` Ted Zlatanov
2012-12-03 9:52 ` Steinar Bang
2012-12-10 21:18 ` Steinar Bang
2016-03-06 20:10 ` Dave Abrahams
2016-03-07 13:37 ` Ted Zlatanov
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=m2hapjtyqx.fsf@pluto.luannocracy.com \
--to=dave@boostpro.com \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.com \
/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).