From: storm@cua.dk (Kim F. Storm)
Cc: ding@gnus.org
Subject: Re: display-time, mail-icon and POP3 mailboxes
Date: 13 Feb 2002 01:27:31 +0100 [thread overview]
Message-ID: <5x4rkmfcp8.fsf__19713.6891809807$1042212443@kfs2.cua.dk> (raw)
In-Reply-To: <m3u1sm4q4f.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> storm@cua.dk (Kim F. Storm) wrote:
> > I haven't debugged this specifically with emacs, but in other
> > programs, it has been necessary to make connect non-blocking with
> > fcntl(s,F_SETFL,O_NONBLOCK) and then use the writefds of select to
> > know when the connect has completed (at least on GNU/Linux).
>
> See also <URL:http://cr.yp.to/docs/connect.html>.
Nice summary, thanks!
In any case, I think it would make sense for open-network-stream
to have an optional 5th argument which serves two purposes:
If it is omitted or nil, the current blocking connect is used.
If it is non-nil, a non-blocking connect is attempted - if supported
by the o/s (and the emacs code) - and when the connection is
established, the argument (which must be a function) is called to
initiate using the connection. The arguments to that function will
probably be the process and buffer (this is still TBD).
If the o/s (or emacs) does not support non-blocking connect, a
blocking connect will be performed - and the supplied function will
simply be called before open-network-stream returns (it may need
an arg indicating whether a blocking or non-blocking connect was made
to arrange for different things to happen when open-network-stream
returns).
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-02-13 0:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3ofj1fwhj.fsf@Janik.cz>
[not found] ` <200202081357.g18Dvfw05454@aztec.santafe.edu>
[not found] ` <m3bsezk837.fsf@Janik.cz>
[not found] ` <5x1yfva7m8.fsf@kfs2.cua.dk>
2002-02-10 18:39 ` Pavel Janík
2002-02-10 19:57 ` Kim F. Storm
[not found] ` <5xn0yhrtye.fsf@kfs2.cua.dk>
2002-02-11 18:48 ` Richard Stallman
2002-02-11 23:31 ` Kim F. Storm
[not found] ` <a49p7s$657$1@quimby2.netfonds.no>
2002-02-12 16:25 ` Jan Vroonhof
[not found] ` <5x3d07iojn.fsf@kfs2.cua.dk>
2002-02-12 16:32 ` Paul Jarc
[not found] ` <m3u1sm4q4f.fsf@multivac.cwru.edu>
2002-02-13 0:27 ` Kim F. Storm [this message]
[not found] ` <5x4rkmfcp8.fsf@kfs2.cua.dk>
2002-02-14 3:12 ` Richard Stallman
2002-02-14 9:41 ` Kim F. Storm
[not found] ` <5xlmdwe6ym.fsf@kfs2.cua.dk>
2002-02-15 10:36 ` Richard Stallman
2002-02-13 15:38 ` Richard Stallman
2002-02-13 22:13 ` Kim F. Storm
[not found] ` <5x3d0558tf.fsf@kfs2.cua.dk>
2002-02-15 10:37 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='5x4rkmfcp8.fsf__19713.6891809807$1042212443@kfs2.cua.dk' \
--to=storm@cua.dk \
--cc=ding@gnus.org \
/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.
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 NNTP newsgroup(s).