Optimized means of keeping a sync'ed history of classes

[mphuff]

I find that retrieving a total list of performance summaries is a taxing operation, especially for some of my users with 1000+ classes. I am hoping to have an operation of this nature and perhaps I'm missing something obvious but I do not see a means of effectively emulating the OTF app:

1. Retrieve historical_bookings via otf-api
2. Validate my latest performance summary I have saved (via my own database)
3. Only pull performance summaries via get_performance_summaries for bookings I retrieved in step (1) but that are newer than I have in the database

Is there a means of doing this that maybe isn't documented? If a Booking also happened to have a performance summary ID this could be done.

[NodeJSmith]

@mphuff Take a look at this prerelease and the new get_workouts method it introduces. I believe this will give you what you need with less overhead.

It does currently pull telemetry and performance summaries for each workout using threaded calls, but it allows providing start/end dates so you can do that for just the ones that are new. There will be a standard release version coming out soon as well, so you won't have to rely on the prerelease version.

[NodeJSmith]

Actually have a new release with the functionality now, so you won't need to use a pre-release. Let me know if the new functionality works for you