From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: gnus-sync ideas
Date: Thu, 16 Dec 2010 11:19:15 -0600 [thread overview]
Message-ID: <87sjxxr5yk.fsf@lifelogs.com> (raw)
In-Reply-To: <m3oc8l8zvc.fsf@quimbies.gnus.org>
On Thu, 16 Dec 2010 17:08:07 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> So, data-sync.el would let you:
>>
>> 1) choose a storage backend, which can be many things but will at least
>> have the choice to be a file (which, of course, can use Tramp).
>>
>> 2) query a key and find out the latest value, data type, CAS key, and
>> timestamp (you'd use the CAS key in the CAS ops below)
>>
>> 3) set a key with a data type (unconditionally or CAS)
>>
>> 4) delete a key (unconditionally or CAS)
>>
>> 5) merge data into a key with a data type and a policy (overwrite,
>> prepend, append, set-if-present, set-if-absent) (unconditionally or CAS)
>>
>> 6) do all of the above as a batch
LMI> If there's one thing that the nnimap experience shows, then it's that
LMI> round trips kill you. So ideally the client would issue just one
LMI> command, like
LMI> GIVE-ME-DATA-CHANGED-SINCE 12167121621 <filter that says what data I want>
LMI> and then we'd just get a stream of data back.
LMI> So all CRUD operations to the store has to be timestamped and
LMI> categorised for this to be fast, I think.
All of the above can be batched, yes, and the query will have just one
timestamp instead of one per key.
LMI> As for how to actually store things like, say, the group topics... I
LMI> don't really have a clear idea how that would actually look...
ELisp, of course. It's just like reading them back from the newsrc.eld file.
Ted
next prev parent reply other threads:[~2010-12-16 17:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 17:57 Separating marks from other group configuration Lars Magne Ingebrigtsen
2010-12-13 18:49 ` Steinar Bang
2010-12-13 19:14 ` Lars Magne Ingebrigtsen
2010-12-15 16:32 ` gnus-sync ideas (was: Separating marks from other group configuration) Ted Zlatanov
2010-12-15 19:18 ` gnus-sync ideas Lars Magne Ingebrigtsen
2010-12-15 21:26 ` Ted Zlatanov
2010-12-16 16:08 ` Lars Magne Ingebrigtsen
2010-12-16 17:19 ` Ted Zlatanov [this message]
2010-12-16 10:06 ` Julien Danjou
2010-12-16 16:33 ` Ted Zlatanov
2010-12-16 18:08 ` Steinar Bang
2010-12-17 15:55 ` Philipp Haselwarter
2010-12-17 16:12 ` Lars Magne Ingebrigtsen
2010-12-17 22:19 ` Steinar Bang
2010-12-18 13:45 ` Ted Zlatanov
2010-12-19 20:08 ` Steinar Bang
2010-12-27 15:22 ` Ted Zlatanov
2010-12-29 22:07 ` Steinar Bang
2010-12-14 10:02 ` Separating marks from other group configuration Julien Danjou
2010-12-14 12:04 ` Steinar Bang
2010-12-14 14:45 ` Philipp Haselwarter
2010-12-15 19:47 ` Lars Magne Ingebrigtsen
2010-12-15 20:29 ` Philipp Haselwarter
2010-12-15 20:32 ` Lars Magne Ingebrigtsen
2010-12-15 19:45 ` Lars Magne Ingebrigtsen
2010-12-15 20:38 ` Steinar Bang
2010-12-15 20:42 ` Lars Magne Ingebrigtsen
2010-12-16 10:12 ` Julien Danjou
2010-12-16 15:50 ` Lars Magne Ingebrigtsen
2010-12-16 16:17 ` Julien Danjou
2010-12-16 16:20 ` Lars Magne Ingebrigtsen
2010-12-16 16:27 ` Julien Danjou
2010-12-16 16:33 ` Lars Magne Ingebrigtsen
2010-12-16 16:49 ` Julien Danjou
2010-12-16 16:18 ` 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=87sjxxr5yk.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).