[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Asynchronous DNS
From: |
Eli Zaretskii |
Subject: |
Re: Asynchronous DNS |
Date: |
Tue, 09 Feb 2016 19:00:10 +0200 |
> From: Alain Schneble <address@hidden>
> CC: Eli Zaretskii <address@hidden>, <address@hidden>
> Date: Tue, 9 Feb 2016 10:02:33 +0100
>
> `process-contact', `set-process-filter', `set-process-filter-multibyte',
> `set-process-window-size', `set-network-process-option',
> `set-process-coding-system', `process-filter-multibyte-p',
> `process-datagram-address', `set-process-datagram-address',
> `process-send-region', `process-send-string', `process-send-eof'
>
> Maybe the last three wouldn't be candidates as they throw an error even
> in the current implementation in case the process status is still
> 'connect, as you and I pointed out already in earlier notes.
But if the wait is for the 'run' status, then it will fix those
problems as well (as I think we should).
- Re: Asynchronous DNS, (continued)
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/07
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/07
- Re: Asynchronous DNS, Alain Schneble, 2016/02/08
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/08
- Re: Asynchronous DNS, Alain Schneble, 2016/02/08
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/08
- Re: Asynchronous DNS, Alain Schneble, 2016/02/09
- Re: Asynchronous DNS, Lars Ingebrigtsen, 2016/02/09
- Re: Asynchronous DNS,
Eli Zaretskii <=
- Re: Asynchronous DNS, Alain Schneble, 2016/02/09
- Re: Asynchronous DNS, Eli Zaretskii, 2016/02/09
- 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