unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: GNU Emacs: Client/Server
Date: 29 Jan 2004 13:41:17 +0100	[thread overview]
Message-ID: <m3fzdzsz9u.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <20040129111259.67CF418B@frontend3.messagingengine.com>

"Dhruva Krishnamurthy" <gnu@furby.fastmail.fm> writes:

> Hello,
>  The fact that "emacsclient" does not build on MS Windows platform
>  (correct me if I am wrong), we end up depending on "gnuserv"
>  functionality. This is *NOT* part of distribution and therefore makes it
>  difficult to keep update with changes in "gnuserv" (if there are any,
>  recently).
> 
>  I was toying with the idea of making the GNU Emacs behave as a client or
>  server through command line options or Elisp functions.
> 
> (On Microsoft Platform on which I work)
> For server:
> - Create a server thread which will use some IPC (mail slots or named
> pipes kernel object) through which Elist expressions can be exchanged
> which can be evaluated by the server

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-

If you have specific ideas how to do this, you are welcome to discuss
them here.


Alternatively, can't you just use an oridinary stream socket on some
random port of your choice?


> Could we use the above approach and do away with the gnuserv/emacsclient
> dependency?

I would suppose that if it is done properly, the emacs server side for
Windows would then be the same as for the currently supported platform
(except for initial setup, of course).

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  parent reply	other threads:[~2004-01-29 12:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 11:12 GNU Emacs: Client/Server Dhruva Krishnamurthy
2004-01-29 12:03 ` Jan D.
2004-01-29 12:13   ` Dhruva Krishnamurthy
2004-01-29 16:18     ` Kim F. Storm
     [not found]       ` <20040130045855.1A6A92E@frontend3.messagingengine.com>
2004-01-30 10:38         ` Kim F. Storm
2004-01-30 10:31           ` Dhruva Krishnamurthy
2004-01-30 13:03             ` Kim F. Storm
2004-02-01  8:01           ` Richard Stallman
2004-02-01 23:49             ` Kim F. Storm
     [not found]               ` <20040202092212.C73932E@frontend3.messagingengine.com>
     [not found]                 ` <m3isipwuog.fsf@kfs-l.imdomain.dk>
     [not found]                   ` <jwvr7xdjz98.fsf-monnier+emacs/devel@asado.iro.umontreal.ca>
     [not found]                     ` <m31xpdwgot.fsf@kfs-l.imdomain.dk>
     [not found]                       ` <jwvektdifzf.fsf-monnier+emacs/devel@asado.iro.umontreal.ca>
     [not found]                         ` <20040203044651.3E26A31@frontend3.messagingengine.com>
     [not found]                           ` <jwvektc5jed.fsf-monnier+emacs/devel@asado.iro.umontreal.ca>
2004-02-05  9:52                             ` Dhruva Krishnamurthy
2004-02-05 15:05                               ` Stefan Monnier
2004-02-06  5:37                                 ` Dhruva Krishnamurthy
2004-02-06  9:52                                   ` David Kastrup
2004-02-06 10:02                                     ` Dhruva Krishnamurthy
2004-02-06 13:36                                   ` Stefan Monnier
2004-02-07 19:32                                   ` Richard Stallman
2004-01-29 12:41 ` Kim F. Storm [this message]
2004-01-29 12:17   ` Dhruva Krishnamurthy
2004-01-29 13:46     ` Roman Belenov
2004-01-30  5:04       ` Dhruva Krishnamurthy
2004-01-29 15:35 ` Stefan Monnier
2004-02-02 15:15   ` Lőrentey Károly
2004-02-02 16:01     ` 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

  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=m3fzdzsz9u.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    /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).