On Tue, Jan 12, 2016 at 11:27:40AM +0100, Oswald Buddenhagen wrote:
> On Tue, Jan 12, 2016 at 10:11:50AM +0100, Philippe Bruhat (BooK) wrote:
> > The fact that the remote Store is the Master was implied,
> > but never explicitely stated.
> >
> but that's just plain wrong. mbsync doesn't impose such a limitation -
Actually, I meant to add "usually" or "by convention", but it got lost
during multiple rewordings... Sorry about that.
I know that there's no such limitation, since my current configuration
is exactly the revese (local MaildirStore listed as master, and remote
IMPAStore as slaves). I was wondering if that could cause issues.
My understanding was that it was a widely used convention, and that it
might have some implicit consequences.
> it's purely conventional to do it like that (and necessary, when you use
> MaxMessages, as the handling is asymmetric, but it's still the user who
> determines the assignment).
OK, thanks for the explanation. So this is one of the consequences.
Reading the documentation, MaxMessages seems to be the only option that
makes the handling asymmetric. Am I right?
So in the end, the decision to make a store the Master really is "this
is one the one that holds everything I care about".
--
Philippe Bruhat (BooK)
In war, the only winners are those who sell the weapons.
(Moral from Groo #3 (Image))
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
