Archived
This forum has been archived. Please start a new discussion on GitHub.
Suggestion on paging implementation
Hi,
We are using Ice 3.5.1.
Client: Win XP
Server: Win Server2008
We use request/response paradigm.
One of the request we send to the server might result in a compressed data size (proto-buf) of over 10MB. We understand that Ice can handle upto 2GB.
We do not want to send anything over 2MB as part of the response, instead we want to break the response into chunks and send it to client. This essentially translates paging.
Given this, from an implementation perspective, I was thinking, conceptually, the client would have to make several calls (request/response) until all the pages are read.
Does that make sense?
Is that the correct approach?
Would you recommend any other approaches?
Regards,
Vishwa
We are using Ice 3.5.1.
Client: Win XP
Server: Win Server2008
We use request/response paradigm.
One of the request we send to the server might result in a compressed data size (proto-buf) of over 10MB. We understand that Ice can handle upto 2GB.
We do not want to send anything over 2MB as part of the response, instead we want to break the response into chunks and send it to client. This essentially translates paging.
Given this, from an implementation perspective, I was thinking, conceptually, the client would have to make several calls (request/response) until all the pages are read.
Does that make sense?
Is that the correct approach?
Would you recommend any other approaches?
Regards,
Vishwa
0
Comments
-
Hi,
Split the response content in chunks/pages is the recommended approach, we recommend that to transfer large files, see How do I transfer a file with Ice?, the recommendation applies to other use cases where client and server exchange large amounts of data.
How to best apply it to your application will depend on the details, as first approach you do as the file system example read bytes until you get a empty sequence.0
