HttpClient and response design

[Vincent Massol]

Title: RE: [Vote] Vote for a new Cactus committer

Hi,   One thing I find strange is that the response is actually stuffed in the method object (GetMethod, ...). So you use the method object for both setting the request and accessing the result. I would think it is better to separate the 2 and provide a response object class.   What do you think ?   Also, the default is to use the disk to store the results. Is that because the design is to read all waiting data from the stream at once and stuff it either on disk or in memory ? This is fine for some cases but there are cases, when it is preferable to leave the data on the server so that it is consumed bit after bit during the processing logic in the application code ... [sorry, I haven't looked closely at the code there to know the exact behaviour]   What do you think ?   Thanks -Vincent