🚀 go-pugleaf

I my application I use a person table with a photo
When this table grows large the client application is some time busy caching
the data.

Using packetrecords and request on demand works fine for startup
but once clicking last or using locate the whole data set is cached.


I read some solutions for that : Let the user reduce the requested records
by a filter or selection list.

Im thinking about overloading the last en locate procedures from CDS
and using the RequestData procedure from TProvider.
for example CDS->Provider->RequestData("Locate XXXX");
The Provider Component on the server should handle this requests.
so the result should be a data set with 10-> 20 records around the requested
record.  For the user it looks like he can scroll fast and the locate takes
some longer.


Has anybody experience with this ?
Or some other suggestions.

Thanks for any help!
Klaas