Manish Moorjani wrote:
Hi Mike,
Thanks for the quick response.
What I mean by partial response is as follows :
When I try accessing the url directly the application can do do things
1) Returns the response in one go
2) Keep on flushing after some data is fetched(say there are total 100 records,
Hi Manish,
Just to echo Orwin's comments, what you're asking should be handled at
the application level, instead of the protocol level (HTTP). It sounds
like what you want is paging. My suggestion would be to control the
location and size of the values returned by passing in additional
Hi,
I am using HttpClient for automatic login into third Party Applications and then
fetching the page and displaying it to the end user.
The page I am trying to fetch queries the database based on a search key and fetches
more than 2000 records to display on the screen.
I am using the
Hello Manish,
What you're doing here looks good. It sounds like you're getting a
socket read timeout which is caused by a large delay when reading the
response. I'm not sure what you mean by read partial responses. The
only options I can think of are setting the SO_TIMEOUT to a higher