[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Asynchronous DNS
From: |
Lars Ingebrigtsen |
Subject: |
Re: Asynchronous DNS |
Date: |
Tue, 09 Feb 2016 11:40:19 +1100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Andreas Schwab <address@hidden> writes:
> Alain Schneble <address@hidden> writes:
>
>> True, but my assumption was that it would be illegal to call
>> `accept-process-output' say, for example, from within
>> `set-process-coding-system' for the sake of waiting for the DNS resolve
>> to complete as it might have unwanted side effects.
>
> You have to wait for the completion event in some way.
Yeah, these blockers would basically have to be a version of this thing
from `send_process':
while (! new_function_that_says_the_process_is_ready (proc))
wait_reading_process_output (0, 20 * 1000 * 1000, 0, 0, Qnil, NULL, 0);
I think. Which is what send_process does on EWOULDBLOCK.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
- Re: Asynchronous DNS, (continued)
- Re: Asynchronous DNS, Eli Zaretskii, 2016/02/08
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/08
- Re: Asynchronous DNS, Eli Zaretskii, 2016/02/09
- Re: Asynchronous DNS, Andreas Schwab, 2016/02/08
- Re: Asynchronous DNS, Alain Schneble, 2016/02/08
- Re: Asynchronous DNS, Andreas Schwab, 2016/02/08
- Re: Asynchronous DNS, Alain Schneble, 2016/02/08
- Re: Asynchronous DNS, Andreas Schwab, 2016/02/08
- Re: Asynchronous DNS,
Lars Ingebrigtsen <=
- Re: Asynchronous DNS, Alain Schneble, 2016/02/09
- Re: Asynchronous DNS, Alain Schneble, 2016/02/09
- Re: Asynchronous DNS, Eli Zaretskii, 2016/02/07
- Re: Asynchronous DNS, Alain Schneble, 2016/02/07
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/07
- Re: Asynchronous DNS, John Wiegley, 2016/02/08
- Re: Asynchronous DNS, Rasmus, 2016/02/08
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/08
- Re: Asynchronous DNS, Eli Zaretskii, 2016/02/08
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/06