Dear list.
First, thank you for the great software. I appreciate its flexibility
achieved through the detailed configuration options.
I am going to use isync with a store containing about 10^5 messages.
My provider has a limit on the number of messages it can hold; thus
I would like to keep all of them on the local store and a smaller
number of them on the remote store.
There is a great option MaxMessages for things like this, but it
automatically erases ("deletes") the messages from the slave store,
while I would need to keep the expired messages intact (or even
better, to erase them on the master store and keep them on the slave).
If you decide so, I would suggest adding an option in the Channels
section, looking like this:
EraseExpired {None|Master|Slave|Both} default: Slave
(Another usecase of this feature would be to allow users e.g. to sync
the flags (on the separate chammel) only on the newest n messages,
which would reduce the time needed to sync.)
Please, would it be hard to implement this? Or would it be against
the philosophy of isync?
Best regards,
Tomas "trosos" Tintera
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
