unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Kim F. Storm" <storm@cua.dk>, Richard Stallman <rms@gnu.org>,
	jan.h.d@swipnet.se, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: GNU Emacs: Client/Server
Date: 05 Feb 2004 10:05:01 -0500	[thread overview]
Message-ID: <jwvk731tvv2.fsf-monnier+emacs/devel@asado.iro.umontreal.ca> (raw)
In-Reply-To: <20040205095216.528FC31@frontend3.messagingengine.com>

>  Based on the suggestion I had on implementing a emacs client/server in
>  pure Elisp, I have come up with a working _Prototype_. The code needs
>  lot of cleanup and I am sure can be improved a lot. This is my first
>  shot at Elisp programming, I request you to kindly help.

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 we
want instead is to extend server.el and emacsclient.c with support for TCP
sockets (and maybe add an elisp version of emacsclient.c).

> - Server accepts a *secret* word which is then used to validate all
> client connections
>   Ex: (emacsserver-start "secret")

I'd prefer an automatically generated random string, but it otherwise
looks reasonable.


        Stefan

  reply	other threads:[~2004-02-05 15:05 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 [this message]
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
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=jwvk731tvv2.fsf-monnier+emacs/devel@asado.iro.umontreal.ca \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=rms@gnu.org \
    --cc=storm@cua.dk \
    /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).