From: Helmut Eller <helmut@xaital.km4u.net>
Cc: emacs-devel@gnu.org
Subject: Re: New patch for server sockets and datagram (UDP) support.
Date: Thu, 7 Mar 2002 18:32:32 +0100 [thread overview]
Message-ID: <200203071732.SAA17748@xaital.online-marketwatch.com> (raw)
In-Reply-To: <5xvgc8nyw0.fsf@kfs2.cua.dk> (no-spam@cua.dk)
no-spam@cua.dk (Kim F. Storm) writes:
> > It's probably a pain to parse keyword arguments in C, but it frees you
> > from overloading positional arguments in an unnatural way. It would
> > also be quite nice to use from Lisp. Another advantage is that you
> > could add new arguments without much backward compatibility
> > restrictions.
>
> It still has the problem of what to do with unknown arguments --
> but at least it will not trigger the debugger due to an incorrect
> number of arguments.
Raise an "invalid keyword" error. That's the pain it was talking
about.
> > I propose
> > to make gethostbyname and related functions available to Lisp. IP
> > addresses could be represented by vectors of 4 bytes (it's a pity that
> > 32bit don't fit into a ELisp fixnum).
> >
>
> Not that I object to this in general, but for what purpose?
Because there is currently no way to get the IP address(es) of the
current host. It MAY also simplify the C level implementation,
because you could require that e.g. the SERVICE argument is actually a
port number and not a string or a number; similar for the HOST
argument.
> > Yet another point: please, please, please make accept-connection a
> > separate function. Then one could make a _blocking_ accept; also
> > accept with a timeout argument would be possible.
>
> I understand that you want to serialize the connections.
> Why is it necessary to do that?
It's probably not necessary in 95% of all uses, but it may be hard to
change later if you hardwire the current behavior. And, about every
socket interface I have seen so far has a separate accept function.
Here is a somewhat artificial example. I would like to control Emacs
from an external Common Lisp program. I would also like to control
the Common Lisp program from Emacs. Do to this I implemented a very
naive rpc mechanism: both sides send their commands via a socket
connection to the peer, the peer evals the command and sends the
result back to the client. Now the problem: if the command include a
recursive/nested calls to caller, serialization is an issue. The
cleanest thing is to accept exactly one connection at a time. Of
course, it is not very hard to come up with different solution, but
accept-connection makes this particular use elegant and reliable.
> And you can start a timer to cancel the accept (by calling
> delete-process) if a connection hasn't been received.
> The sentinel can cancel (or restart) that timer if a
> connection is accepted.
Yes I could. But a blocking accept is easier to use and more
reliable.
If you think a separate function is to much trouble, leave it out.
Helmut.
_______________________________________________
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 17:32 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200203071732.SAA17748@xaital.online-marketwatch.com \
--to=helmut@xaital.km4u.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.