From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: lorentey@elte.hu (=?iso-8859-2?q?L=F5rentey_K=E1roly?=) Newsgroups: gmane.emacs.devel Subject: Re: GNU Emacs: Client/Server Date: Mon, 02 Feb 2004 16:15:27 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20040129111259.67CF418B@frontend3.messagingengine.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1075738559 6996 80.91.224.253 (2 Feb 2004 16:15:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 2 Feb 2004 16:15:59 +0000 (UTC) Cc: Emacs Devel Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Feb 02 17:15:48 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Angjk-0001uH-00 for ; Mon, 02 Feb 2004 17:15:48 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1Angjj-00038k-00 for ; Mon, 02 Feb 2004 17:15:47 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1Angi0-0002Ah-13 for emacs-devel@quimby.gnus.org; Mon, 02 Feb 2004 11:14:00 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AngBp-0004jY-PL for emacs-devel@gnu.org; Mon, 02 Feb 2004 10:40:45 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1Anfnc-0007nl-CL for emacs-devel@gnu.org; Mon, 02 Feb 2004 10:16:17 -0500 Original-Received: from [157.181.151.9] (helo=mx2.elte.hu) by monty-python.gnu.org with esmtp (Exim 4.24) id 1Anfna-0007le-T3 for emacs-devel@gnu.org; Mon, 02 Feb 2004 10:15:43 -0500 Original-Received: from eris (eris.elte.hu [157.181.150.146]) by mx2.elte.hu (Postfix) with ESMTP id 66D02B2708; Mon, 2 Feb 2004 16:15:31 +0100 (CET) Original-Received: by eris (Postfix, from userid 1000) id 3016D47C3F; Mon, 2 Feb 2004 16:15:27 +0100 (CET) Original-To: Stefan Monnier User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux) X-ELTE-SpamVersion: SpamAssassin 2.60 X-ELTE-VirusStatus: clean X-ELTE-SpamCheck: no X-ELTE-SpamCheck-Details: score=-4.9, required 5.9, BAYES_00 -4.90 X-ELTE-SpamLevel: X-ELTE-SpamScore: -4 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:19661 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:19661 Stefan Monnier writes: > I feel like the best way forward is to support TCP sockets rather than = only > unix sockets. This would be an improvement under Unix and would give u= s > W32 support "for free". What improvement would it provide under a GNU or UNIX system? I think everything that the TCP server implementation would provide is already not just possible, but secure and convenient with ssh. In a multi-user system, it is possible that dozens of Emacs servers are run simultaneously by different users. How would emacsclient decide which network port the user's own instance listens on? Having to remember arbitrary network port numbers is IMO not very user-friendly. I think client$ ssh server emacsclient is much more convenient than client$ emacsclient --host server --port 24352 Furthermore, the former command already works nicely, and it supports opening new Emacs frames on the client side---both X and (in my arch branch) terminal frames. Implementing something similar in the raw TCP case would require extensive changes that are IMHO simply not worth the effort. UNIX domain sockets are useful and secure; I don't see why they should be abandoned. --=20 K=E1roly