From: Ulrich Mueller <ulm@kph.uni-mainz.de>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Server protocol (was: Re: error in server-running-p on M$)
Date: Sun, 23 Nov 2008 09:14:41 +0100 [thread overview]
Message-ID: <18729.4337.83437.732524@a1ihome1.kph.uni-mainz.de> (raw)
In-Reply-To: <f7ccd24b0811222019mfc17894v5f5c446298fa6c01@mail.gmail.com>
>>>>> On Sun, 23 Nov 2008, Juanma Barranquero wrote:
>> Let me explore further if there is a simpler way to handle this.
> If you want to propose changes to the way the TCP connections and
> authentication files are used, please do it in a way compatible with
> 22.X...
It is incompatible already:
Client 22 connecting to server 23:
$ emacsclient-emacs-22 foo
Waiting for Emacs...
-error Unknown&_command:&_/local/home/ulm/foo
Client 23 connecting to server 22:
$ emacsclient-emacs-23 foo
Waiting for Emacs...
*ERROR*: Unknown message: Authentication failed
The above is with TCP. With Unix sockets it is much worse, because
the connection succeeds but the information sent by the client is
misinterpreted by the server, resulting in several garbage buffers
(the following is for client 23 connecting to server 22):
,----
| CRM Buffer Size Mode File
| .% -current-frame 0 Fundamental /dev/pts/-current-frame
| *scratch* 0 Lisp Interaction
| * *Messages* 302 Fundamental
| foo 6 Fundamental ~/foo
| -file 0 Fundamental ~/-file
| xterm 0 Fundamental ~/xterm
| % 2 0 Fundamental /dev/pts/2
| % -tty 0 Fundamental /dev/pts/-tty
`----
This makes me wonder if the client shouldn't send some token
identifying the protocol version, which would be checked by the
server.
Ulrich
next prev parent reply other threads:[~2008-11-23 8:14 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 11:44 error in server-running-p on M$ dhruva
2008-11-22 11:58 ` Juanma Barranquero
2008-11-22 12:51 ` Eli Zaretskii
2008-11-22 13:00 ` Juanma Barranquero
2008-11-22 13:20 ` Eli Zaretskii
2008-11-22 13:37 ` Juanma Barranquero
2008-11-22 13:53 ` Eli Zaretskii
2008-11-22 14:13 ` Ulrich Mueller
2008-11-22 14:17 ` Juanma Barranquero
2008-11-22 14:29 ` Ulrich Mueller
2008-11-22 14:36 ` Juanma Barranquero
2008-11-22 15:35 ` Ulrich Mueller
2008-11-22 16:04 ` Juanma Barranquero
2008-11-22 16:52 ` Ulrich Mueller
2008-11-22 21:47 ` Juanma Barranquero
2008-11-23 3:56 ` dhruva
2008-11-23 3:59 ` Juanma Barranquero
2008-11-23 4:01 ` dhruva
2008-11-23 4:03 ` Juanma Barranquero
2008-11-23 4:10 ` dhruva
2008-11-23 4:15 ` Juanma Barranquero
2008-11-23 4:17 ` dhruva
2008-11-23 4:19 ` Juanma Barranquero
2008-11-23 8:14 ` Ulrich Mueller [this message]
2008-11-23 11:33 ` Server protocol (was: Re: error in server-running-p on M$) Juanma Barranquero
2008-11-23 16:33 ` dhruva
2008-11-23 17:48 ` Juanma Barranquero
2008-11-23 4:02 ` error in server-running-p on M$ Stefan Monnier
2008-11-23 4:10 ` Juanma Barranquero
2008-11-23 5:21 ` Stefan Monnier
2008-11-23 5:32 ` Juanma Barranquero
2008-11-23 5:57 ` Stefan Monnier
2008-11-23 11:26 ` Juanma Barranquero
2008-11-23 12:46 ` Juanma Barranquero
2008-11-23 13:13 ` Ulrich Mueller
2008-11-24 2:55 ` Stefan Monnier
2008-11-24 14:46 ` Juanma Barranquero
2008-11-24 15:10 ` Ulrich Mueller
2008-11-24 15:16 ` Juanma Barranquero
2008-11-24 15:34 ` Ulrich Mueller
2008-11-24 15:45 ` Juanma Barranquero
2008-12-09 20:46 ` Stefan Monnier
2008-12-10 7:05 ` Chetan Pandya
2008-12-10 12:59 ` Juanma Barranquero
2008-12-10 18:30 ` Stefan Monnier
2008-12-10 18:47 ` Juanma Barranquero
2008-12-11 2:07 ` Stefan Monnier
2008-12-11 16:30 ` Juanma Barranquero
2008-12-11 18:47 ` Stefan Monnier
2008-12-12 0:40 ` Juanma Barranquero
2008-12-12 4:51 ` Stefan Monnier
2008-12-12 8:19 ` Juanma Barranquero
2008-12-12 18:49 ` Stefan Monnier
2008-12-12 20:20 ` Juanma Barranquero
2008-11-23 3:58 ` Stefan Monnier
2008-11-23 3:59 ` Stefan Monnier
2008-11-23 4:12 ` Juanma Barranquero
2008-11-23 5:19 ` Stefan Monnier
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=18729.4337.83437.732524@a1ihome1.kph.uni-mainz.de \
--to=ulm@kph.uni-mainz.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=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 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.