From: Magnus Henoch <mange@freemail.hu>
Subject: Re: Problems with the url package on w32?
Date: Sat, 02 Dec 2006 12:37:18 +0100 [thread overview]
Message-ID: <871wniv89d.fsf@freemail.hu> (raw)
In-Reply-To: 87lkltztzy.fsf@freemail.hu
Does anyone know what to do about this?
> Mathias Dahl <brakjoller@gmail.com> writes:
>
>>> Does (make-network-process :name "http" :buffer "http-localhost"
>>> :host "127.0.0.1" :service 80
>>> :nowait t)
>>> work?
>>
>> I get no error but it returns `nil'. I guess it should return a
>> process object, right?
>
> Yes. Does it work with hosts other than localhost?
[ it doesn't ]
> The direct cause of the `nil' return value is this code in process.c:
>
> if (s < 0)
> {
> /* If non-blocking got this far - and failed - assume non-blocking is
> not supported after all. This is probably a wrong assumption, but
> the normal blocking calls to open-network-stream handles this error
> better. */
> if (is_non_blocking_client)
> return Qnil;
>
> This seems to be a bug of some sort. The documentation doesn't
> mention that make-network-process might ever return nil. I see four
> possible solutions; someone who knows Windows should look at this.
>
> 1. Make non-blocking connections work on Windows.
> 2. Make (featurep 'make-network-process '(:nowait t)) return nil on
> Windows.
> 3. Document that make-network-process returns nil if it fails to
> create a non-blocking socket.
> 4. Make make-network-socket do a blocking connect if a non-blocking
> connect fails, and document that.
>
> Magnus
next parent reply other threads:[~2006-12-02 11:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ur6vodg5m.fsf@gmail.com>
[not found] ` <871wnnclkz.fsf@freemail.hu>
[not found] ` <uac2acxu0.fsf@gmail.com>
[not found] ` <87lkltztzy.fsf@freemail.hu>
2006-12-02 11:37 ` Magnus Henoch [this message]
2006-12-03 3:15 ` Problems with the url package on w32? Richard Stallman
2006-12-03 18:25 ` Magnus Henoch
2006-12-03 21:17 ` Kim F. Storm
2006-12-19 15:48 ` Kim F. Storm
2006-12-19 23:13 ` Juanma Barranquero
2006-12-20 11:05 ` Kim F. Storm
2006-12-20 12:05 ` Juanma Barranquero
2006-12-19 23:45 ` Lennart Borgman
2006-12-19 23:54 ` Juanma Barranquero
2006-12-20 0:04 ` Lennart Borgman
2006-12-20 0:08 ` Juanma Barranquero
2006-12-20 6:57 ` Eli Zaretskii
2006-12-20 9:07 ` Juanma Barranquero
2006-12-20 10:52 ` Eli Zaretskii
2006-12-20 11:06 ` Juanma Barranquero
2006-12-20 21:41 ` Stefan Monnier
2006-12-20 23:13 ` Juanma Barranquero
2006-12-21 22:47 ` Stefan Monnier
2006-12-21 22:56 ` Juanma Barranquero
2006-12-21 23:31 ` Stefan Monnier
2006-12-21 23:13 ` Lennart Borgman
2006-12-22 21:48 ` Stefan Monnier
2006-12-23 0:33 ` Lennart Borgman
2006-12-21 1:02 ` Lennart Borgman
2006-12-21 10:03 ` Lennart Borgman
2006-12-04 5:15 ` Richard Stallman
2006-12-04 8:55 ` Kim F. Storm
2006-12-05 1:45 ` Richard Stallman
2006-12-20 11:22 LENNART BORGMAN
2006-12-20 14:36 ` Kim F. Storm
2006-12-21 11:52 ` Jason Rumney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871wniv89d.fsf@freemail.hu \
--to=mange@freemail.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).