[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Asynchronous DNS
From: |
Lars Ingebrigtsen |
Subject: |
Re: Asynchronous DNS |
Date: |
Mon, 15 Feb 2016 15:22:20 +1100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Stefan Monnier <address@hidden> writes:
> 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?
We could if that were the only function that had this problem. I'm not
confident we would be able to do this for all the process related
functions in a way that wouldn't break anything.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
- Re: Asynchronous DNS, (continued)
- 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, 2016/02/14
- Re: Asynchronous DNS,
Lars Ingebrigtsen <=
- 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
- Re: Asynchronous DNS, Andreas Schwab, 2016/02/15