| QUOTE (RavenMaster @ September 12, 2013 05:32 pm) |
| I see. So, if i understood correctly, even the "Get Newest" can't be applied cause GSAK can't compare the number of recent logs missing in your DB with the ones on the GS server, so it would download only the difference. |
Yes, and no.
As the get logs api does not allow date searches we can't be exact about the process, and do it 100% efficiently. However, we can do it more efficiently than the current "guess" the number of logs approach.
I see the benefit of doing this via a macro or natively in GSAK is that it can be automated so the user does not have to "guess" how many logs to fetch to get the missing logs.
So the process would go something like:
1. Fetch x number of logs (where x is the number of logs to initially fetch - I suggest a number between 10 and 30)
2. Check to see if the newest log in the GSAK database is in the logs just fetched. If it is, then add all logs in the fetched batch that are not already in the database - end of story, as we should now be up to date.
3. If at step 2 the original newest GSAK log is not found then we add those just fetched, then loop back to step one (perhaps then fetching the default of 30 to take care of situations where there are a large number of logs to fetch), etc.