From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Dhruva Krishnamurthy" Newsgroups: gmane.emacs.devel Subject: Re: GNU Emacs: Client/Server Date: Thu, 29 Jan 2004 17:47:53 +0530 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20040129121753.A53CF376@frontend3.messagingengine.com> References: <20040129111259.67CF418B@frontend3.messagingengine.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1075380820 11517 80.91.224.253 (29 Jan 2004 12:53:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 29 Jan 2004 12:53:40 +0000 (UTC) Cc: Emacs Devel Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Jan 29 13:53:36 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 1AmBfs-00030g-00 for ; Thu, 29 Jan 2004 13:53:36 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AmBfr-0006EB-00 for ; Thu, 29 Jan 2004 13:53:36 +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 1AmBZU-0001R9-58 for emacs-devel@quimby.gnus.org; Thu, 29 Jan 2004 07:47:00 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AmBNB-0006gu-8O for emacs-devel@gnu.org; Thu, 29 Jan 2004 07:34:17 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AmB8b-0004NF-5U for emacs-devel@gnu.org; Thu, 29 Jan 2004 07:19:45 -0500 Original-Received: from [66.111.4.32] (helo=frontend3.messagingengine.com) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AmB7R-00046C-KY for emacs-devel@gnu.org; Thu, 29 Jan 2004 07:18:01 -0500 Original-Received: by frontend3.messagingengine.com (Postfix, from userid 99) id A53CF376; Thu, 29 Jan 2004 07:17:53 -0500 (EST) Content-Disposition: inline X-Mailer: MIME::Lite 1.2 (F2.72; T1.001; A1.60; B2.21; Q2.21) Original-To: "Kim F. Storm" X-Sasl-Enc: Zom7rmcLQW+nhpsvToBNpg 1075378673 In-Reply-To: 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:19539 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:19539 On 29 Jan 2004 13:41:17 +0100, "Kim F. Storm" said: > If we could enhance make-network-process to support either of these > connection types (both as client and server), I don't see why not. > > I guess it would be a different :family, e.g. :family mailslot, with > suitable new ADDRESS format for :local and :remote addresses, and then > extend the process code to handle such connections/servers as any other > kind of service. > > I don't know what it takes to handle connection setup, input/output, > etc., so I cannot say whether it can be done through the normal process- > I suggested Mail Slots as I had worked on implementing it in one of my projects (controlling a profiling session on a remote computer). It was very easy to implement it and hence suggested as a way to achieve IPC. Also, there is not much difference between Mail slot communication on local computer or remote computer (it is abstracted). Anyway, my views are based on development on MS Win32. with regards, dhruva ________________________________________ Dhruva Krishnamurthy Proud FSF member: #1935 http://schemer.fateback.com/