DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=upkxbqgyglQ3niQ4mIFL7hf9LEX9Gwe44b2xS3qKpKd5khRR7pMo2yA0FLdg3oestXNRycXhbrHxdRpcbZhauatKSqfQptvhG+irbNKRgsSfDE5J/LZYPSf3u4Qlxed10lzLWzvNWjnHpeWqRta8LU7SWGXmcpD2dYx10Qh1So8=;
Date: Wed, 23 Jan 2008 17:02:03 -0800 (PST)
From: JumpJet Mailbox <jumpjetinfo@yahoo.com>
Subject: [gopher] Re: Strategy: end of Gopher in Mozilla
To: gopher@complete.org
In-Reply-To: <4295158.1200924389492.JavaMail.root@ps30>
MIME-Version: 1.0
Content-type: text/plain
Content-Transfer-Encoding: 8bit
Message-ID: <895429.67078.qm@web35515.mail.mud.yahoo.com>
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

Glad to see that someone (other than JumpJet) is using GopherS.  That Server software has got to be the absolute easiest to get up and running (6 minutes is typical).
"mdbird@lineone.net" <mdbird@lineone.net> wrote:  I am not sure I am a typical Gopher user there may be no such thing but=20
I thought I would give my views on the future strategy.

I started using Gopher three years ago as a way of challenging=20
students on my Networking course who had their own web servers at home=20
and thought they knew everything about network servers.

Obviously Gopher is an exotic and certainly is not a preparation for=20
the future and I have been subject to snide comments from colleagues=20
about teaching outdated technologies.

But I cite two main reasons for persisting with Gopher servers.

On lower level courses I use GopherS on Windows XP as my Gopher=20
Server.
This introduces the students to the concept of services run by the=20
operating system and the notion of servers using different ports. Also=20
by using a range of client software from Lynx, Hgopher, WSgopher,=20
Firefox and even patched IE 6.
I can clearly demonstrate that how a client interaction with the same=20
server software can produce vastly differing results depending on the=20
features of the client software. The students are genuinely intrigued=20
to find out that there are other ways of serving web pages and=20
concealing a website within a Gopher server. This is where Firefox=20
stands head and shoulders above the other clients it is very capable=20
delivering a diverse range of file types from Gopher servers. Whereas=20
older clients just spew out HTML code from Gopher servers. For my=20
students a simple fully featured client that deals with web pages is a=20
must to gain their acceptance of Gopher. In the long term the community=20
must ensure that such clients will continue to be available to those=20
that will follow on after us. Lynx, Hgopher and WSgopher just don=E2=80=99t=
cut=20
it as far as my students are concerned.

On higher level courses I use Bucktooth on Ubuntu Linux as my Gopher=20
Server.
This introduces students to the concept of daemons (inetd and xinetd)=20
TCP/IP services and wrappers. Bucktooth is a fine example of the power=20
of PERL and its installation scripts are an effective simple=20
demonstration of how PEARL scripts should work.

For me Gopher provides a different and interesting way of showing how=20
things really work rather than just using the safe sanitised offerings=20
of today, that make things so simple that students don=E2=80=99t fully=20
understand what they have achieved.

Regards

Mike Bird


__________________________________________________
Get up to =C2=A3150 by recycling your old mobile - visit www.tiscali.co.uk/=
recycle


---------------------------------
Never miss a thing.   Make Yahoo your homepage.