hi Ura,
>> Want to send the reply in pieces. By example i have a file with 1000 records and want to send the data in sets of 100. Something similar (i think) to NetWebBrowse settings / Options when loading method is page and records per page are a defined number.
This is do'able, but you need to think about your API that you are offering to the user. Remember this is all just a request and a response. If the user wants smaller pieces then you need to give him the opportunity to _ask_ for smaller pieces.
For example at the moment you have a function that says;
"GetMeAllTheRecords".
but maybe it would be better to have something like;
"GetMeAllNewRecords" or "GetMeAllRecordsAfterDateTime" or "GiveMe10RecordsFromID" and so on.
Obviously these aren't the right method names <g> - but the idea is that you give the user some parameters in your current method to ask for a "subset" of everything you have. As long as the user can figure out what they do have, and ask for anything missing, you should be good to go.
Obviously the exact approach will vary depending o your data set, but for "incremental updates" the most common is to stamp records with some sort of date & time of last change, then the client can ask for "everything that has changed since xxx,xxx". Oh with a "max" parameter. So they can ask for "everything that has changed since xxx,xx - max 10 records". You give them the first 10, they then repeat the question using the last received time as the time of their next starting point.
Cheers
Bruce
Cheers
Bruce