|
From: Oswald B. <osw...@gm...> - 2025-11-10 09:05:22
|
On Mon, Nov 10, 2025 at 08:31:55AM +0000, syn...@da... wrote: >On Fri, Oct 31, 2025 at 12:15:55PM +0100, Oswald Buddenhagen via isync-devel wrote: >>shoehorning isync into doing something it was not designed for > >What is so extreme about what I am doing? > isync's purpose is to keep both sides in sync. MaxMessages is a deviation from that. when you push that number down to zero, that's _literally_ extreme, and you've gone from syncing to fetching. >Why is this such a difficult task for isync? > because MaxMessage doesn't really fit the basic scheme, its implementation actually comes at a rather significant cost in complexity; it's easily the most difficult part of the whole codebase. i don't know if it would be difficult to make it support zero; it might just work with a few minor changes. patches (with autotests) welcome. |