Thanks Daniel !!!
Actually I want to wait for some time to receive response from server.
And that is the reason I am using multi handle perform with only one
easy handle in it.
Otherwise using only easy handle perform I would have to implement my
own wait loop. Also my application should not block for respose rather
it should continue sending othre messages if any.
Do you think any other logic can be used for scenario ?

I think will try to add easy_handle into multi_handle stack before each
transfer.

--
Nilesh
Daniel Stenberg wrote:
> On Mon, 29 May 2006, Nilesh wrote:
>
>>>>   /*This function does typical curl_multi_peroform operation and 
>>>> check for return status */
>>>
>>>
>>> Are you saying this repeatedly calls curl_multi_perform() until the 
>>> whole process is complete or are you just calling 
>>> curl_multi_perform() once in this function?
>>
>>
>> Calling it once. I am using almosy similar code given in example 
>> directory and multi-single.c file
>
>
> The multi-single.c example calls curl_multi_perform() repeatedly until 
> that single transfer is done. So should you, if you want a complete 
> transfer to take place.
>
>> Ok. Anyway my URL is the same. Only thing I want to change is data 
>> which will be posted to same URL again and again.
>> So as I understand  before I do perform with new data and same 
>> multi_handle -
>> - cleanup already used easy_handle
>
>
> No
>
>> - create new easy_handle and add it to multi_handle stack
>
>
> No, add the same handle again.
>
>> Is that the case ? why can't same handle be used ?
>
>
> No. It can.
>
> Your problem is rather that you're not doing the curl_multi_perform() 
> calls properly. Why use the multi interface at all if you're not using 
> the non-blocking ability?
>
>