The reason what I do that( add while(1) ) is to verify the sock_cb activate
after the events exits. If the application always check the fifo in the
event loop without leaving, the sock_cb never activates.

that's why I'm so confused with the behavior.
If I replace the fifo with a socket, the sock_cb will activate after
waiting all message received completely.
That makes me hardly receive message and handle the message(such as
download the message requested) asynchronously.

Maybe I need to try other interface to finish my plan !?

2017-05-02 22:57 GMT+08:00 Daniel Stenberg <daniel_at_haxx.se>:

> On Tue, 2 May 2017, Pahome Chen wrote:
>
> *while(1); *// I add this line to block the function but I already
>>> add easy handle to multi handle
>>>
>>
>> Didn't we already discuss that hyperfifo runs single-threaded and if you
>>> loop unconditionally there then no transfer will occur?
>>>
>>
>> sorry I still don't know why it has relation with single-threaded?
>>
>
> Because your addition of while(1) above makes the code never leave that
> function so it can't continue and do the rest of what it needs to do. It
> get stuck in that loop.
>
> You can of course fix that by removing the while(1) again.
>
> --
>
> / daniel.haxx.se
>

-- 
Best Regards,
pahome

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2017-05-03