From: "Juanma Barranquero" <lekktu@gmail.com>
Subject: Back to emacsclient/server
Date: Mon, 23 Oct 2006 16:14:20 +0200 [thread overview]
Message-ID: <f7ccd24b0610230714xc1f7a92m4ad59df40f048d7e@mail.gmail.com> (raw)
I'm finally getting the time to try implementing TCP sockets (and so
Win32 support) for emacsclient.c/server.el. I must confess that the
talk about reimplementing gnuserv in Java has made me shiver quite a
lot (no offense intended, I just happen to not like Java *at all*).
I've reviewed all comments exchanged about this issue in past threads
(or at least all the ones I could find). There were some decisions
that got more-or-less universal agreement, some that were
controversial, and a few that were left undecided (mostly because we
were throwing ideas back and forth).
So let's recapitulate:
- The server (i.e., server.el) should:
- Have an option to choose among Unix (if available) or TCP sockets.
- Have an option to specify the host address, defaulting to 127.0.0.1.
- Choose the port at random (to allow multiple server in the same computer).
- Write the hostname address, port and random authentication string
in a file.
- Close any connection which doesn't start with "-auth
AUTHENTICATION-STRING".
- The client (emasclient.c) should:
- Interpret --server-name as an Unix socket (if available), and, if
that does fail, as a path to the server file.
- Default --server-name to an environment variable
(EMACS_SERVER_NAME, for example), if -server-name is missing.
- Send "-auth AUTHENTICATION-STRING" as the first command in any connection.
There was some discussion about allowing/not allowing remote
connections (defaulting to "not allow"). If they're allowed, either a
option in server.el would activate remote connection support, or
perhaps just the fact that server-host != 127.0.0.1 should suffice. I
favor this, because connections on Unix sockets will never be remote,
so a new option seems redundant. But I don't care much.
Stefan wanted that --server-name=foo, if not valid as a Unix socket,
would try to open server file ~/.emacs.server/foo to get the address,
port and authentication string. I'm not so sure. I don't see why root
in one session cannot try to connect with Emacs in another user's
session, so --server-name is gonna need to be a (relative or absolute)
path, and not a name depending of the current user. Am I missing
something?
The last time around, about 80% of the above was implemented; I'll
have to rework it because I got rid of the Unix socket support (which
must stay), but it shouldn't be too difficult.
--
/L/e/k/t/u
next reply other threads:[~2006-10-23 14:14 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 14:14 Juanma Barranquero [this message]
2006-10-23 14:54 ` Back to emacsclient/server Jason Rumney
2006-10-23 19:48 ` Stefan Monnier
2006-10-23 21:17 ` Jason Rumney
2006-10-23 22:02 ` Andreas Schwab
2006-10-23 16:00 ` Ted Zlatanov
2006-10-23 20:09 ` Eli Zaretskii
2006-10-24 0:02 ` Ted Zlatanov
2006-10-24 4:35 ` Eli Zaretskii
2006-10-24 15:36 ` Ted Zlatanov
2006-10-24 17:31 ` Eli Zaretskii
2006-10-24 19:24 ` Ted Zlatanov
2006-10-24 22:22 ` Stefan Monnier
2006-10-25 16:33 ` Ted Zlatanov
2006-10-25 11:46 ` Michael Olson
2006-10-25 12:38 ` David Kastrup
2006-10-23 21:47 ` Juanma Barranquero
2006-10-23 23:50 ` Ted Zlatanov
2006-10-24 2:01 ` Stefan Monnier
2006-10-24 15:40 ` Ted Zlatanov
2006-10-24 18:17 ` Stefan Monnier
2006-10-24 19:31 ` Ted Zlatanov
2006-10-23 16:26 ` Jan D.
2006-10-23 19:52 ` Stefan Monnier
2006-10-23 20:35 ` Jan Djärv
2006-10-23 21:20 ` Jason Rumney
2006-10-23 21:59 ` Jason Rumney
2006-10-24 5:06 ` Jan Djärv
2006-10-24 8:37 ` Juanma Barranquero
2006-10-24 13:27 ` Jason Rumney
2006-10-23 21:57 ` Juanma Barranquero
2006-10-24 5:08 ` Jan Djärv
2006-10-24 7:32 ` Kim F. Storm
2006-10-23 19:46 ` Stefan Monnier
2006-10-23 21:54 ` Juanma Barranquero
2006-10-24 2:04 ` Stefan Monnier
2006-10-24 8:39 ` Juanma Barranquero
2006-10-27 0:27 ` Juanma Barranquero
2006-10-27 11:08 ` Juanma Barranquero
2006-10-27 12:21 ` Jason Rumney
2006-10-27 13:25 ` Stefan Monnier
2006-10-27 13:35 ` Juanma Barranquero
2006-10-27 13:29 ` Juanma Barranquero
2006-10-27 13:50 ` Slawomir Nowaczyk
2006-10-27 14:20 ` Stefan Monnier
2006-10-27 15:18 ` Juanma Barranquero
2006-10-28 18:13 ` Richard Stallman
2006-10-30 1:02 ` Stefan Monnier
2006-10-31 0:35 ` Juanma Barranquero
2006-10-28 7:27 ` Richard Stallman
2006-10-28 21:16 ` Juanma Barranquero
2006-10-28 23:38 ` Kim F. Storm
2006-10-30 13:33 ` Richard Stallman
[not found] ` <f7ccd24b0610271000p16dda672mb146860725d47e00@mail.gmail.com>
[not found] ` <45426C6B.10401@student.lu.se>
[not found] ` <f7ccd24b0610271400x343c7197jbd6b775f49834924@mail.gmail.com>
[not found] ` <454276CB.9000002@student.lu.se>
[not found] ` <f7ccd24b0610271419p51bf429fjf5fb548e613cd950@mail.gmail.com>
[not found] ` <45427A24.8020107@student.lu.se>
[not found] ` <f7ccd24b0610271438r64539e94j6b17c251b213a047@mail.gmail.com>
[not found] ` <45427F8E.5040507@student.lu.se>
[not found] ` <f7ccd24b0610271700v472f9c53v43017fce05e761e9@mail.gmail.com>
2006-10-28 0:24 ` Juanma Barranquero
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=f7ccd24b0610230714xc1f7a92m4ad59df40f048d7e@mail.gmail.com \
--to=lekktu@gmail.com \
/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).