Re: Emacs Cloud (coverage and killed groups)

[Lars Ingebrigtsen <larsi@gnus.org>]

I had originally thought of the Cloud stuff being totally symmetrical,
but perhaps that's not the best approach here.

That is, at home I have a Gnus setup that contains a gazillion servers,
and some of them are local, like nnml ones.  These obviously shouldn't
be replicated to other instances.  Fine.

But what happens to the topic topology?  If we push out newsrc data that
contains only these replicated groups initially (and I think that's the
right solution), what happens if we move a group from one topic to
another in one of the other instances?  We can't just do a full new dump
of the topology back to the "home" instance, because it no longer
contains all the groups...

So I'm now thinking we have to have a strict division between one "home"
instance that contains everything, and that can do full chunk dumps.
And then all the other instances would just log updates like

"read articles 56-69 in group foo.bar"
"moved group foo.bar from topic Zot to topic Bar"

The other non-home instances would pull these in as needed, and the
"home" instance, too.

The main problem, though, is that if you're not on your home instance
for months, the number of incremental chunks might get pretty ... huge.

But that may not actually be much of a problem.

Hm...

What do all y'all think?

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/