Re: gnus sync

[Steinar Bang <sb@dod.no>]

>>>>> Steinar Bang <sb@dod.no>:
> [snip!]
>> If you GET a server, eg. 
>> https://myserver/gnussync/backends/nntp/news.gmane.org
>> you will get a list with two members "parameters" and "groups"

>> I haven't given much thought to the behaviour of
>> https://myserver/gnussync/backends/nntp/news.gmane.org/parameters
> [snip!]

>> If you GET a group, you will get a lisp, or JSON list containing two
>> members: "parameters" and "marks".

>> I haven't given much thought to the behaviours of group parameters,
>> like eg.
>> https://myserver/gnussync/backends/nntp/news.gmane.org/groups/gmane.emacs.gnus.general/parameters
> [snip!]
> When I think about it, and as was discussed in a recent thread, the
> contents here, is something I really would prefer to see managed by a
> VCS (like my .emacs and .gnus.el files are...).

> On the other hand, one of the "cloud(y) gnus" requirements, was that
> distributing everything gnus to a priestine gnus should "just work".

> And that would definitely include the server and group parameters into
> what should be synced...

But how should .gnus.el-specified group parameters, like the one Tassilo
Horn showed in the "Where are group parameters stored?" thread, fit into
this picture...?  Perhaps the way they do today?  How are they combined
today, btw?

Reference to the article showing the .gnus.el example:
 http://thread.gmane.org/gmane.emacs.gnus.general/79418/focus=79447