What is the different between sync and cache

[ramibb]

Hi,

I would like to cache my all gmail account since their is no cache all , i will choose cache 10000

but what is the option message to sync compare with message to cache ?

Thanks

[ramibb]

I will try to answer to myself 

I think it means you can sync 10000 but cache only 500 of them , that gives the choice not to cache all the synced mails

I just want them on my phone , i think its more confusing than helping

please correct me if I'm wrong

[Kostya Vasilyev]

You'll usually want it the other way around: to sync <= to cache.

"To sync" -- how many most recent messages the app looks at, every time it checks mail, to keep up to date.

This is how many show when you open a folder.

About those messages, Aqua knows that 1) they still exist on the server and 2) their flags (read/unead, starred).

"To cache" -- older messages, previously synced as "messages to sync", beyond the *current* "messages to sync" setting.

Will now show when you open a folder -- since Aqua doesn't know if they still exist on the server, and their flags.

Will be used if you scroll down a folder to see more messages, to speed up the loading time.

Are trimmed from the device's storage automatically over time as necessary.

[this_is_nascar]

So, does that mean that the number set as "to cache" is the number of messages kept on the device and available to be shown by AM?


Sent from my XT1254 using Tapatalk

[Kostya Vasilyev]

Re: So, does that mean that the number set as "to cache" is the number of messages kept on the device and available to be shown by AM?

Yes

Re: and available to be shown by AM

No

When you open a folder's message list, the app shows the (usually) smaller number, "messages to sync" -- those messages which are *known* to still exist on the server and in a known state (read/unread etc.)

The "messages to cache" comes into play if you scroll a folder's message list down to "see more" -- then the app can more quickly re-sync the next .... messages just by checking with the server for their existence and state (as opposed to full download).

Another way to see all those cached messages is to do menu -> view -> offline list (in message list view). This is done automatically if the device is in airplane mode.

[StR]

Kostya,

Please, consider posting your explanation above (or a more "brushed" version of it) to the FAQ.

Until reading this explanation I was fully convinced that "messages to sync" sets the maximum number of new messages to download, whereas "messages to cache" sets the number of messages kept on the device.

I guess the terminology is somewhat ambiguous. Essentially, "messages to cache" is talking about "cached message information" (as opposed to complete messages), but that wouldn't be a clear term either.
I don't know what would be unambiguous terms. That's why a clear explanation should be easily available.

[Kostya Vasilyev]

Re: Essentially, "messages to cache" is talking about "cached message information" (as opposed to complete messages), but that wouldn't be a clear term either.

Not, it's not just "information" -- and message text is "information" too, I mean (usually) the text of a message isn't fully random.

It's whatever was loaded into the app previously, and left there once it drops off the tail end of "messages to sync" but not updated until either the user scrolls down or deleted when it drops beyond "messages to cache" (and then deleted).

[this_is_nascar]

So, if I change the cache setting, will that trim the number of messages contained on the device/database?

Meaning, if I've been running with a cache setting of 10k, my expectation is that up to 10k messages in each folder are on the phone.  If I change that to 5k, do I risk losing half my mail/messages from my phone?


Sent from my XT1254 using Tapatalk

[StR]

It's whatever was loaded into the app previously, and left there once it drops off the tail end of "messages to sync" but not updated until either the user scrolls down or deleted when it drops beyond "messages to cache" (and then deleted).

So, does that include the bodies of the messages (and if configured so, attached images, etc.) that were previously synced but are now beyond the tail end of "messages to sync"?  Your description three posts above sounded like it doesn't include that, but only the "service" information about those messages.

Sorry for trying to clarify this, - I am not nitpicking here, - but just trying to understand it fully.
And I see that confusion about these two settings is common among AM users.

[mikeone]

...
Sorry for trying to clarify this, - I am not nitpicking here, - but just trying to understand it fully.
And I see that confusion about these two settings is common among AM users.

Thanks StR,
I'm also a little "confused"... not really, but the functionality behind the option "messages to cache" is actually somewhat complex to understand.

[this_is_nascar]

Look at all my posts and what I post about.  It's obvious that I'm confused as well .


Sent from my XT1254 using Tapatalk

[this_is_nascar]

So, if I change the cache setting, will that trim the number of messages contained on the device/database?

Meaning, if I've been running with a cache setting of 10k, my expectation is that up to 10k messages in each folder are on the phone.  If I change that to 5k, do I risk losing half my mail/messages from my phone?  What about from the mail server?


Sent from my XT1254 using Tapatalk

Eagerly waiting a response.  Thanks in advance.


Sent from my XT1254 using Tapatalk

[Kostya Vasilyev]

Re: So, if I change the cache setting, will that trim the number of messages contained on the device/database?

Yes

Re: If I change that to 5k, do I risk losing half my mail/messages from my phone

Don't understand the "risk" here. Yes, this is exactly what's supposed to happen.

Phone storage is not infinite. Neither is network bandwidth and quotas. Or the battery.

Therefore, this app -- just like K9 Mail, Gmail and countless other mobile apps -- is carefully, intentionally designed to only sync and to only store a limited number of messages on your mobile device.

You can think of the app as a "window" into your "real" messages on the server, "sliding" and "dropping messages off the tail end" as time goes on.

[this_is_nascar]

OK, thanks.

Sent from my XT1254 using Tapatalk

[StR]

Kostya,

I suspect you may have missed the question that got buried in the middle of the thread.
I'd appreciate if you can clarify this:

It's whatever was loaded into the app previously, and left there once it drops off the tail end of "messages to sync" but not updated until either the user scrolls down or deleted when it drops beyond "messages to cache" (and then deleted).

So, does that include the bodies of the messages (and if configured so, attached images, etc.) that were previously synced but are now beyond the tail end of "messages to sync"?  Your description three posts above sounded like it doesn't include that, but only the "service" information about those messages.

Sorry for trying to clarify this, - I am not nitpicking here, - but just trying to understand it fully.
And I see that confusion about these two settings is common among AM users.