unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Port of Emacs client / server programs to Windows NT
Date: Mon, 30 Oct 2006 09:56:56 +0100	[thread overview]
Message-ID: <4545BE58.9010807@student.lu.se> (raw)
In-Reply-To: <20061030072212.GA2665@janet>

Neil Roberts wrote:
> Granted that is true, so there would be no harm in leaving TCP support
> and presumably implementing it for the Unix build as well. However as
> the current default is to use named pipes and TCP sockets aren't even
> implemented under the regular Unix version surely that implies that
> the preferred solution is to use Unix domain sockets?
>   

It may solve another problem on w32 too. The software firewalls jumps in 
if you are using TCP. As far as I understand it this will not happen 
with pipes (but I am not sure).

Can't w32 pipes have access protection on them too?

  reply	other threads:[~2006-10-30  8:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-28  9:06 Port of Emacs client / server programs to Windows NT Neil Roberts
2006-10-28  9:28 ` Jason Rumney
2006-10-30  0:56 ` Stefan Monnier
2006-10-30  0:59   ` David Kastrup
2006-10-30  1:16     ` Stefan Monnier
2006-10-30  7:22   ` Neil Roberts
2006-10-30  8:56     ` Lennart Borgman [this message]
2006-10-30  9:11       ` Neil Roberts
2006-10-30  9:30         ` Lennart Borgman
2006-10-30 10:16           ` Kim F. Storm
2006-10-30 10:39             ` Lennart Borgman
2006-10-30 11:00               ` Jason Rumney
2006-10-30 14:17                 ` Neil Roberts
2006-10-30 20:01                   ` Juanma Barranquero
2006-10-30 20:37             ` Eli Zaretskii
2006-10-30 14:10     ` Stefan Monnier
2006-10-30  0:58 ` 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=4545BE58.9010807@student.lu.se \
    --to=lennart.borgman.073@student.lu.se \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).