From: Paul Michael Reilly <pmr@pajato.com>
Cc: emacs-devel@gnu.org
Subject: Re: Gnuserv
Date: Sun, 22 Oct 2006 15:18:52 -0400 [thread overview]
Message-ID: <453BC41C.8020204@pajato.com> (raw)
In-Reply-To: <453B4A8C.7000101@gnu.org>
Jason Rumney wrote:
> Paul Michael Reilly wrote:
>> Most of the culprit is "Unable to connect, connection refused" type
>> messages.
> What makes you think rewriting gnuserv using another programming
> language will solve these problems?
Because in fifteen minutes I had a server/client pair working just
dandy, server spawned from Emacs, based on the Java KnockKnock tutorial
code. Now to flesh it out by working on the protocol, where I should be
working, not wondering what freaking network issue in the C code is
causing an inability to connect. And it handles multiple connections
just fine. Bottom line is that with C code, the coder has to worry
about OS dependencies and quirks. With Java (and some other languages
no doubt) the VM eliminates these issues in a platform independent way.
Were I a C based networking guru, this is a non issue but I'm not and I
have the itch so following the path of least resistance is the path for me.
However, I do suspect that Jetty is a better answer in the long run
because it opens up http. First things first though.
-pmr
next prev parent reply other threads:[~2006-10-22 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 5:10 Gnuserv Paul Michael Reilly
2006-10-22 10:40 ` Gnuserv Jason Rumney
2006-10-22 11:56 ` Gnuserv David Hansen
2006-10-22 19:18 ` Paul Michael Reilly [this message]
2006-10-23 11:45 ` Gnuserv Richard Stallman
2006-10-23 12:22 ` Gnuserv Paul Michael Reilly
2006-10-22 13:22 ` Gnuserv 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=453BC41C.8020204@pajato.com \
--to=pmr@pajato.com \
--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).