From: "Gopher-Project" <gopher-project-bounces+rachael=telefisk.org@lists.alioth.debian.org>
Date: Sat Feb 1 18:43:43 2014
Subject: [gopher] White Mesa node-gopher server 0.1.0 released
--===============2965684467932647603==
Content-Type: multipart/alternative; boundary=001a1135f1808b665904f15bd270
--001a1135f1808b665904f15bd270
Content-Type: text/plain; charset=ISO-8859-1
Hi,
'node-gopher' is an RFC 1436 gopher server implemented as a node.js app
including a CGI facility, logging in Common Log format with rotation,
gophermap support, and more. It runs on Linux and Windows. Of course
node.js must be installed on the host. Here are links to a README file and
the source tarball:
http://www.whitemesa.net/node-gopher/README.txt
http://www.whitemesa.net/node-gopher/node-gopher-0.1.0.tgz
or better yet, get them from the main menu of a running instance of
node-gopher:
gopher://whitemesa.net:7070/
or the original White Mesa 'Purple Sage' gopher server
gopher://whitemesa.net/
Stress testing with Apache JMeter indicates that performance is very
robust. Compared to my multi-threaded reference server (written in C++,
running as a Windows service) the node server, running on the same host, is
as fast or faster handling file transfers (large or small) under heavy
load. However, it's not as fast processing gophermaps or directory listings
(by a factor of 3). Maybe my javascript code for these processing tasks
needs refinement. Python script based dynamic content works just fine using
the node.js facilities to implement CGI (look on the main menu of the White
Mesa gopher server at port 7070 for current 'space weather' info delivered
this way). I also notice that the node.js server generally uses a lot more
memory than the native C++ service.
Anyway, what started out as a node.js prototype service project took on a
life of its own and I thought I'd put the source out there in case someone
can make use of it. The server is easy to set up on Windows or Linux; just
unpack the tarball, tweak the config file as needed, open a terminal window
and invoke node: 'node server.js'.The README covers basic features and
config file stuff and details can be studied by inspecting the source code.
I'm no node.js expert so I'm sure there is room for improvement. The
structure of a node.js application may seem strange at first, with its
event driven, non blocking I/O model. You can read more at nodejs.org.
Comments and bug reports are welcome.
Cheers,
Bob NW8L
--001a1135f1808b665904f15bd270
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi,<div><br></div><div>'node-gopher' is an RFC 143=
6 gopher server implemented as a node.js app including a CGI facility, logg=
ing in Common Log format with rotation, gophermap support, and more. It run=
s on Linux and Windows. Of course node.js must be installed on the host. He=
re are links to a README file and the source tarball:</div>
<div><br></div><div><a href=3D"http://www.whitemesa.net/node-gopher/README.=
txt">http://www.whitemesa.net/node-gopher/README.txt</a></div><div><a href=
=3D"http://www.whitemesa.net/node-gopher/node-gopher-0.1.0.tgz">http://www.=
whitemesa.net/node-gopher/node-gopher-0.1.0.tgz</a></div>
<div><br></div><div>or better yet, get them from the main menu of a running=
instance of node-gopher:</div><div><br></div><div>gopher://<a href=3D"http=
://whitemesa.net:7070/">whitemesa.net:7070/</a></div><div><br></div><div>
or the original White Mesa 'Purple Sage' gopher server</div><div><b=
r></div><div>gopher://<a href=3D"http://whitemesa.net/">whitemesa.net/</a><=
/div><div><br></div><div>Stress testing with Apache JMeter indicates that p=
erformance is very robust. Compared to my multi-threaded reference server (=
written in C++, running as a Windows service) the node server, running on t=
he same host, is as fast or faster handling file transfers (large or small)=
under heavy load. However, it's not as fast processing gophermaps or d=
irectory listings (by a factor of 3). Maybe my javascript code for these pr=
ocessing tasks needs refinement. Python script based dynamic content works =
just fine using the node.js facilities to implement CGI (look on the main m=
enu of the White Mesa gopher server at port 7070 for current 'space wea=
ther' info delivered this way). I also notice that the node.js server g=
enerally uses a lot more memory than the native C++ service.<br>
</div><div><br></div><div>Anyway, what started out as a node.js prototype s=
ervice project took on a life of its own and I thought I'd put the sour=
ce out there in case someone can make use of it. The server is easy to set =
up on Windows or Linux; just unpack the tarball, tweak the config file as n=
eeded, open a terminal window and invoke node: 'node server.js'.The=
README covers basic features and config file stuff and details can be stud=
ied by inspecting the source code. I'm no node.js expert so I'm sur=
e there is room for improvement. The structure of a node.js application may=
seem strange at first, with its event driven, non blocking I/O model. You =
can read more at <a href=3D"http://nodejs.org">nodejs.org</a>.</div>
<div><br></div><div>Comments and bug reports are welcome.</div><div><br></d=
iv><div>Cheers,</div><div><br></div><div>Bob NW8L</div></div>
--001a1135f1808b665904f15bd270--
--===============2965684467932647603==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
--===============2965684467932647603==--
(DIR) Followup: Re: [gopher] White Mesa node-gopher server 0.1.0 released
(DIR) Followup: Re: [gopher] White Mesa node-gopher server 0.1.0 released
(DIR) Followup: Re: [gopher] White Mesa node-gopher server 0.1.0 released