On Sat, Jan 08 2022, Oswald Buddenhagen wrote:
> rather "ExpireSide {Far|Near}" - more traditional syntax, and would not
> need duplication when MaxAge finally gets added.Makes sense >>This seems to be the only option that introduces a functional difference >>between the near and far side. >> > "SyncState *" is the other asymmetry, which would actually speak in > favor of optionally decoupling things. Good point, but this seems to imply that storing state remotely would make sense/be possible? Just wondering. > one question would be in how far this actually matters. how often do you > have active contact with this? would hiding it behind a wrapper maybe > sidestep it? It's an annoyance, of course. After the setup, I call mbsync though a script. However it's one of those annoyances that grows on you every time you re-read the configuration to adjust for some changes. You're absolutely right for push-pull also being annoying in this scenario. Making near/far functionally equivalent would result in push/pull suddenly correct itself too, which is why I think it would be nice at least on a conceptual level. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
