From: Kevin Ryde <user42@zip.com.au>
To: Guile-Devel <guile-devel@gnu.org>
Subject: Re: Unbuffered socket I/O
Date: Mon, 26 Feb 2007 09:57:10 +1100 [thread overview]
Message-ID: <87abz13kxl.fsf@zip.com.au> (raw)
In-Reply-To: <87mz34ol6r.fsf@laas.fr> (Ludovic Courtès's message of "Fri, 23 Feb 2007 18:09:16 +0100")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> Is there a reason why `SCM_SOCK_FD_TO_PORT ()' in `socket.c' asks for an
> unbuffered port?
To make send and receive conversations reliable, according to sockets
section in the manual. (I don't think I added that. I hope I'm not
claiming my own words as an authority!)
Also of course send and recv! don't use the buffering, so there's no
point having it when working with packets.
> #define SCM_SOCK_FD_TO_PORT(fd) \
> scm_fdes_to_port (fd, "r", sym_socket)
That's an incompatible change, I think, since it can leave unflushed
data where previously it went straight out.
Perhaps the unbuffering can be reiterated in the manual or docstrings
in each of socket, socketpair and accept which create such ports.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-02-25 22:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 17:09 Unbuffered socket I/O Ludovic Courtès
2007-02-23 22:36 ` Neil Jerram
2007-02-25 22:57 ` Kevin Ryde [this message]
2007-02-26 14:07 ` Ludovic Courtès
2007-02-26 20:32 ` Neil Jerram
2007-02-26 23:35 ` Kevin Ryde
2007-02-27 9:11 ` Ludovic Courtès
2007-02-28 21:24 ` Kevin Ryde
2007-03-01 9:10 ` Ludovic Courtès
2007-03-04 23:48 ` Kevin Ryde
2007-03-07 0:20 ` Kevin Ryde
2007-03-07 0:30 ` Kevin Ryde
2007-03-07 4:45 ` Kevin Ryde
2007-03-07 9:40 ` Ludovic Courtès
2007-02-26 23:27 ` Kevin Ryde
2007-02-28 9:47 ` Ludovic Courtès
2007-02-28 20:59 ` Kevin Ryde
2007-03-01 10:44 ` Ludovic Courtès
2007-03-05 23:15 ` Kevin Ryde
2007-08-07 16:01 ` Ludovic Courtès
2007-05-13 17:13 ` `scm_std_select ()' call in `fport_wait_for_input ()' Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87abz13kxl.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).