From: Alex Schroeder <alex@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: New patch for server sockets and datagram (UDP) support.
Date: Thu, 07 Mar 2002 15:51:37 +0100 [thread overview]
Message-ID: <87it88bfd2.fsf@gnu.org> (raw)
In-Reply-To: <5xbse0pn55.fsf@kfs2.cua.dk> (storm@cua.dk's message of "07 Mar 2002 13:39:50 +0100")
storm@cua.dk (Kim F. Storm) writes:
> Yes, that is the other route we can take - and then also split the
> current TYPE argument into TYPE and FAMILY. I have absolutely no
> objections to doing that -- actually, that it what I originally wanted
> to do, but then I was told that open-network-stream has too
> many arguments already...
Haha, that was a cheap trick, then. :) Anyway, if you provide a list
of special purpose functions as discussed at the end, then this is a
non-issue anyway. Thanks.
>> The initial socket for a DCC connection is created by the side
>> that initiates (Offers) the connection. This socket should be
>> a TCP socket bound to INADDR_ANY, listening for connections.
>
> Ok, I'll add that. The selected port number will be available in
> (cadr (process-contact ddc)) (i.e. the SERVICE element).
Thanks for considering this.
> Alternatively, using something like
> (featurep 'server-sockets)
> (featurep 'datagram-sockets)
> would be a more generic approach.
That would be nice, or combined with the functions you mention next,
this seems good.
> We could rename the C-level function to, say, open-network-connection
> and write lisp-level wrappers (in simple.el) around it like
> open-network-stream, open-network-stream-nowait, open-network-stream-server,
> open-local-stream-nowait, open-local-stream, open-local-stream-server,
> open-datagram-server, open-datagram-client,
> etc. etc.
>
> Then you don't have 10 different C functions all doing variations of
> the same thing, but still the user will have all the `specific-purpose'
> functions handy.
That sounds ok to me because I only care about the Lisp level.
Other people shall judge maintenace issues or code issues on the C
level.
Thanks, Kim.
Alex.
--
http://www.emacswiki.org/
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-07 14:51 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2u1sa7819.fsf@xaital.online-marketwatch.com>
2002-02-21 23:45 ` Non-blocking open-network-stream Kim F. Storm
2002-02-22 16:04 ` Stefan Monnier
2002-02-25 22:38 ` Kim F. Storm
2002-02-26 22:46 ` Helmut Eller
2002-02-27 11:59 ` Kim F. Storm
2002-02-28 4:08 ` Richard Stallman
2002-03-01 0:21 ` Kim F. Storm
2002-03-01 8:01 ` Juanma Barranquero
2002-03-01 10:50 ` Kim F. Storm
2002-03-01 17:10 ` Pavel Janík
2002-03-01 21:23 ` Richard Stallman
2002-03-07 0:08 ` New patch for server sockets and datagram (UDP) support Kim F. Storm
2002-03-07 10:56 ` Kim F. Storm
2002-03-07 11:39 ` Alex Schroeder
2002-03-07 12:39 ` Kim F. Storm
2002-03-07 14:51 ` Alex Schroeder [this message]
2002-03-08 21:06 ` Richard Stallman
2002-03-13 15:56 ` Kim F. Storm
2002-03-13 23:19 ` Final(?) " Kim F. Storm
2002-03-14 0:50 ` Al Petrofsky
2002-03-14 9:30 ` Kim F. Storm
2002-03-14 12:42 ` Richard Stallman
2002-03-14 13:35 ` Kim F. Storm
2002-03-17 22:02 ` I have installed the " Kim F. Storm
2002-03-07 15:18 ` New " Helmut Eller
2002-03-07 16:09 ` Kim F. Storm
2002-03-07 17:32 ` Helmut Eller
2002-03-07 23:58 ` Kim F. Storm
2002-03-08 7:38 ` Helmut Eller
2002-03-08 9:13 ` Kim F. Storm
2002-03-08 11:16 ` Helmut Eller
2002-03-08 16:36 ` Stefan Monnier
2002-03-08 20:57 ` Kim F. Storm
2002-03-08 21:03 ` Stefan Monnier
2002-03-08 21:07 ` Richard Stallman
2002-03-13 15:12 ` Kim F. Storm
2002-03-07 12:54 ` Mario Lang
2002-03-07 12:58 ` Kim F. Storm
2002-03-08 9:09 ` Richard Stallman
2002-03-08 9:35 ` Kim F. Storm
2002-03-08 11:04 ` Helmut Eller
2002-03-02 7:59 ` Non-blocking open-network-stream Helmut Eller
2002-03-03 0:12 ` Kim F. Storm
2002-03-03 10:46 ` Helmut Eller
2002-03-03 16:44 ` Mario Lang
2002-03-03 14:39 ` 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
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=87it88bfd2.fsf@gnu.org \
--to=alex@gnu.org \
--cc=emacs-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.
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).