From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: 100% CPU on TCP servers (on Windoze).
Date: Sat, 15 Jul 2006 18:02:34 -0400 [thread overview]
Message-ID: <jwv4pxir0jb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <f7ccd24b0607150824l17ddc1b2u4b91002c0f4f345a@mail.gmail.com> (Juanma Barranquero's message of "Sat, 15 Jul 2006 17:24:30 +0200")
>> That's for local connections. If you want to allow remote connections, of
>> course you'll use a TCP socket either way (maybe additionally to a unix
>> socket).
>> I see no problem here.
> Uh? Are you proposing that the server can use simultaneously a Unix
> socket for local connections and a TCP socket for remote ones?
Why not, if that's necessary (don't know that it is, and don't know that it
isn't either).
> Or (what I thought) that the server be configurable to use either Unix
> sockets (which would naturally limit the connections to local ones) or
> TCP sockets?
The config var should enable/disable remote connections.
The use of Unix sockets vs TCP sockets is an implementation detail.
Stefan
prev parent reply other threads:[~2006-07-15 22:02 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-06 18:38 100% CPU on TCP servers Juanma Barranquero
2005-08-18 15:51 ` Juanma Barranquero
2005-09-09 12:53 ` Kim F. Storm
2005-09-09 15:25 ` Juanma Barranquero
2005-09-10 7:47 ` Jason Rumney
2005-09-10 23:01 ` Kim F. Storm
2005-10-12 15:07 ` Kim F. Storm
2005-10-12 22:42 ` Juanma Barranquero
2006-07-13 22:35 ` 100% CPU on TCP servers (on Windoze) Kim F. Storm
2006-07-14 8:15 ` Jason Rumney
2006-07-14 9:54 ` Kim F. Storm
2006-07-14 10:54 ` Juanma Barranquero
2006-07-14 9:51 ` Jason Rumney
2006-07-14 10:23 ` Kim F. Storm
2006-07-14 10:43 ` Jason Rumney
2006-07-14 11:14 ` Eli Zaretskii
2006-07-14 10:50 ` Juanma Barranquero
2006-07-14 11:16 ` Kim F. Storm
2006-07-14 11:42 ` Kim F. Storm
2006-07-14 12:27 ` Juanma Barranquero
2006-07-14 13:08 ` Eli Zaretskii
2006-07-14 13:59 ` Jason Rumney
2006-07-14 14:22 ` Kim F. Storm
2006-07-14 14:41 ` Jason Rumney
2006-07-14 17:29 ` Eli Zaretskii
2006-07-14 18:12 ` Stefan Monnier
2006-07-14 15:43 ` Stuart D. Herring
2006-07-14 13:24 ` Kim F. Storm
2006-07-14 13:40 ` Eli Zaretskii
2006-07-14 14:04 ` Kim F. Storm
2006-07-14 15:28 ` Juanma Barranquero
2006-07-14 22:07 ` Kim F. Storm
2006-07-14 23:23 ` Juanma Barranquero
2006-07-15 0:50 ` Kim F. Storm
2006-07-15 2:09 ` Juanma Barranquero
2006-07-15 9:05 ` Eli Zaretskii
2006-07-15 13:54 ` Juanma Barranquero
2006-07-15 14:59 ` Stefan Monnier
2006-07-15 15:30 ` Juanma Barranquero
2006-07-15 20:38 ` Eli Zaretskii
2006-07-15 22:07 ` Stefan Monnier
2006-07-15 17:16 ` Richard Stallman
2006-07-15 2:04 ` Stefan Monnier
2006-07-15 2:11 ` Juanma Barranquero
2006-07-15 11:52 ` Stefan Monnier
2006-07-15 13:50 ` Juanma Barranquero
2006-07-15 14:58 ` Stefan Monnier
2006-07-15 15:24 ` Juanma Barranquero
2006-07-15 22:02 ` Stefan Monnier [this message]
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=jwv4pxir0jb.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).