From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-devel@gnu.org
Subject: Re: Initial SCTP support for the upcoming 1.6.5 release
Date: Tue, 24 Aug 2004 16:15:14 +0200 [thread overview]
Message-ID: <ljacwkhbbh.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <22A81E2B-ED67-11D8-84CE-000D932C78D8@lurchi.franken.de> (Michael Tuexen's message of "Fri, 13 Aug 2004 22:27:02 +0200")
>> As long as SCTP needs an external library and is not supported
>> directly by libc, we think it is better to not include it in
>> guile-core.
>
> Hmm. This might be a bit special. The functions socket, send, recv
> and so on are simply extended to support SCTP. New functions will
> not become part of libc. All SCTP implementations (well, the
> Linux Kernel implementation, the BSD kernel implementation and
> the Solaris implementation) provide the sctp_* functions in a
> libsctp library. This is similar to Solaris, for example, where
> you need to link against a socket library to use socket functions.
> So they is also not part of libc. But, yes, networking is not core
> functionality, it is only needed by some, not by all, programs.
I think I have misunderstood the nature of SCTP. Although one can
argue that networking is not needed by all programs, we nevertheless
do provide sockets in guile-core. So, from the perspective of Guile,
networking clearly is core functionality, right now.
I thought SCTP was a kind of additional protocol for a specific
purpose, like maybe FTP or HTTP. I don't think we should have support
for protocols like this in guile-core. (I did understand that SCTP is
on the same layer as TCP and UDP...)
But as you say, SCTP seems different. The socket function directly
understands the request for SOCK_SEQPACKET (which will use SCTP,
right?) and you can use the read/write syscalls to use such a socket.
Is that correct?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-24 14:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 18:26 Initial SCTP support for the upcoming 1.6.5 release Michael Tuexen
2004-08-11 12:29 ` Michael Tuexen
2004-08-13 13:40 ` Marius Vollmer
2004-08-13 20:27 ` Michael Tuexen
2004-08-24 14:15 ` Marius Vollmer [this message]
2004-08-24 17:35 ` Michael Tuexen
2004-09-08 15:03 ` Marius Vollmer
2004-09-08 15:34 ` Michael Tuexen
2004-08-14 9:59 ` Michael Tuexen
2004-08-16 0:40 ` Kevin Ryde
2004-08-16 10:42 ` Michael Tuexen
2004-08-17 23:46 ` Kevin Ryde
2004-08-19 18:34 ` Michael Tuexen
2004-08-20 1:13 ` Kevin Ryde
2004-08-20 7:57 ` Michael Tuexen
2004-08-16 17:02 ` Michael Tuexen
2004-08-16 18:44 ` Rob Browning
2004-08-20 18:18 ` Michael Tuexen
2004-08-23 0:58 ` Kevin Ryde
2004-08-23 19:54 ` Michael Tuexen
2004-08-24 0:57 ` Kevin Ryde
2004-08-24 11:27 ` Michael Tuexen
2004-08-24 12:46 ` Michael Tuexen
2004-08-24 14:24 ` Marius Vollmer
2004-08-24 18:22 ` Michael Tuexen
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=ljacwkhbbh.fsf@troy.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.de \
--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).