From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: GNU Emacs: Client/Server Date: 06 Feb 2004 08:36:07 -0500 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20040129111259.67CF418B@frontend3.messagingengine.com> <32D82A01-5253-11D8-82BB-00039363E640@swipnet.se> <20040129121313.766CE37D@frontend3.messagingengine.com> <20040130045855.1A6A92E@frontend3.messagingengine.com> <20040202092212.C73932E@frontend3.messagingengine.com> <20040203044651.3E26A31@frontend3.messagingengine.com> <20040205095216.528FC31@frontend3.messagingengine.com> <20040206053754.30BFC4B@frontend NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1076074840 14832 80.91.224.253 (6 Feb 2004 13:40:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 6 Feb 2004 13:40:40 +0000 (UTC) Cc: Emacs Devel Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Feb 06 14:40:35 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 1Ap6Dj-0002hp-00 for ; Fri, 06 Feb 2004 14:40:35 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1Ap6Di-0002kZ-00 for ; Fri, 06 Feb 2004 14:40:35 +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 1Ap6CF-0004ch-5M for emacs-devel@quimby.gnus.org; Fri, 06 Feb 2004 08:39:03 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1Ap6As-0004JS-6L for emacs-devel@gnu.org; Fri, 06 Feb 2004 08:37:38 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1Ap69m-0003ai-Ip for emacs-devel@gnu.org; Fri, 06 Feb 2004 08:37:03 -0500 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.24) id 1Ap69V-0003Dy-Ng for emacs-devel@gnu.org; Fri, 06 Feb 2004 08:36:13 -0500 Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 74B6321392; Fri, 6 Feb 2004 08:36:07 -0500 (EST) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id 5CBEB8C708; Fri, 6 Feb 2004 08:36:07 -0500 (EST) Original-To: "Dhruva Krishnamurthy" In-Reply-To: <20040206053754.30BFC4B@frontend3.messagingengine.com> Original-Lines: 28 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.9, requis 5, BAYES_00 -4.90) 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:19767 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:19767 >> Maybe you know it and you're just experimenting, but I just want to make >> sure you do realize that gnuclient/gnuserver already solve those >> problems, so clearly there isn't much point is creating yet another system. > What about portability and distribution issues since it is written in C? First, my point was at least as much about "change server.el rather than creating a new emasserver.el" than about "modify emacsclient.c instead of creating a new emacsclient.el". One of the reasons for emacsclient.c is that it should be faster to execute. Now this is not necessarily the case and for other reasons I think it might be worthwhile to implement an elisp version of the emacsclient. As far as portability is concerned, it shouldn't be that bad since it's just some TCP socket code in emacsclient.c which AFAIK will only require some header-inclusion-tweaking to get working: the code in itself will hopefully work in both Unix and w32 environments without too much trouble. >> I'd prefer an automatically generated random string, but it otherwise >> looks reasonable. > How will the client know the randomly generated string to establish an > auth'ed connection? Do you suggest that the random string be stored in a > file which only the user invoking the server has access? Yes. Much like Xauth (which gnuserv uses). Stefan