unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Dhruva Krishnamurthy" <devel@member.fsf.org>
Cc: Emacs Devel <emacs-devel@gnu.org>, "Kim F. Storm" <storm@cua.dk>
Subject: Re: GNU Emacs: Client/Server
Date: Fri, 30 Jan 2004 10:34:04 +0530	[thread overview]
Message-ID: <20040130050404.199912E@frontend3.messagingengine.com> (raw)
In-Reply-To: <u8yjq27g9.fsf@intel.com>


On Thu, 29 Jan 2004 16:46:46 +0300, "Roman Belenov" <rbelenov@yandex.ru>
said:
> "Dhruva Krishnamurthy" <devel@furby.fastmail.fm> writes:
> 
> > I suggested Mail Slots as I had worked on implementing it in one of my
> > projects (controlling a profiling session on a remote computer).
> 
> AFAIK they are actually used by gnuserv, so you can reuse the code
> (and it seems to me that the whole idea is just an embedding of
> gnuserv functionality/codes into Emacs executable).
> 

If that is the case, that would be ideal. Since gnuserv is well tested,
it should not be too difficult for seasoned GNU Emacs hackers to embed
it. The big advantage of Mail Slots is the ease of implementation
(atleast on MS platform). It is very easy to come up with clients to talk
to GNU Emacs. Also, the embedding can be done through a DLL or SO if you
do not want to bloat the GNU Emacs executable size. Like a load on demand
stuff. Since the Server feature is something which can be isolated, it
might be a nice idea to decouple it from the main GNU Emacs executable.
This was just a thought on packaging.

with regards,
dhruva
________________________________________
Dhruva Krishnamurthy
Proud FSF member: #1935
http://schemer.fateback.com/

  reply	other threads:[~2004-01-30  5:04 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
2004-01-29 12:17   ` Dhruva Krishnamurthy
2004-01-29 13:46     ` Roman Belenov
2004-01-30  5:04       ` Dhruva Krishnamurthy [this message]
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=20040130050404.199912E@frontend3.messagingengine.com \
    --to=devel@member.fsf.org \
    --cc=emacs-devel@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).