[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Asynchronous DNS
From: |
Alain Schneble |
Subject: |
Re: Asynchronous DNS |
Date: |
Mon, 15 Feb 2016 01:19:24 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (windows-nt) |
Stefan Monnier <address@hidden> writes:
>> (progn
>> (make-network-stream ... :nowait t)
>> (set-process-coding-system ...))
>> would not block.
>
> Why would we have to block?
> Can't set-process-coding-system just set some process fields (to
> remember which coding-system to use) and return, and then use those
> fields later on when the DNS resolution is done?
Yes, that would be a welcome optimization and should be doable with a
small refactoring in set-process-coding-system and
set_network_socket_coding_system, AFAICS.
- Re: Asynchronous DNS, (continued)
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/09
- Re: Asynchronous DNS, Alain Schneble, 2016/02/10
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/11
- Re: Asynchronous DNS, Alain Schneble, 2016/02/12
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/12
- Re: Asynchronous DNS, Alain Schneble, 2016/02/13
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/13
- Re: Asynchronous DNS, Eli Zaretskii, 2016/02/14
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/14
- Re: Asynchronous DNS, Stefan Monnier, 2016/02/14
- Re: Asynchronous DNS,
Alain Schneble <=
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/14
- Re: Asynchronous DNS, Eli Zaretskii, 2016/02/14
- Re: Asynchronous DNS, Alain Schneble, 2016/02/14
- Re: Asynchronous DNS, Eli Zaretskii, 2016/02/14
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/14
- Re: Asynchronous DNS, Alain Schneble, 2016/02/14
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/14
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/15
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/15
- Re: Asynchronous DNS, Eli Zaretskii, 2016/02/15