Timm Murray | 5 Mar 05:56 2004
Picon

Gopher+ Clarification

From the Gopher+ document:

----
A lot of folks need ability to retrieve and display
pictures, but there is no real consensus on ONE format
for these pictures.  We don't want to define a type
character for every oddball  picture type.  Gopher+
handles Pictures, Movies, and Sounds  by defining
three item types: ":" for bitmap images, ";" for
movies, and "<" for sounds (originally I, M, and S
were suggested, but they  were informally in use in
other ways; the only thing magic   about ":", ";", and
"<", is that they are the first  characters after '9')
----

When I first read this, I had thought the ':' type was specifically 
refering to bitmap images of the .BMP veriety.  In other words, the 
raw, uncompressed image data.  But on re-reading it, it seems that 
it's actually implying a deprecation of the  'g' and 'I' types 
("We don't want to define a type character for every oddball picture 
type.") and using only ':' for images, compressed or not, and letting 
the MIME type be more specific.

This seems like a much saner way to go about it.  Is this the correct 
interpretation of the above?

William G. Davis | 5 Mar 16:01 2004
Picon

Re: Gopher+ Clarification

Yes.

--- Timm Murray <tmurray-gopher@...>
wrote:
> From the Gopher+ document:
> 
> ----
> A lot of folks need ability to retrieve and display
> pictures, but there is no real consensus on ONE
> format
> for these pictures.  We don't want to define a type
> character for every oddball  picture type.  Gopher+
> handles Pictures, Movies, and Sounds  by defining
> three item types: ":" for bitmap images, ";" for
> movies, and "<" for sounds (originally I, M, and S
> were suggested, but they  were informally in use in
> other ways; the only thing magic   about ":", ";",
> and
> "<", is that they are the first  characters after
> '9')
> ----
> 
> When I first read this, I had thought the ':' type
> was specifically 
> refering to bitmap images of the .BMP veriety.  In
> other words, the 
> raw, uncompressed image data.  But on re-reading it,
> it seems that 
> it's actually implying a deprecation of the  'g' and
> 'I' types 
(Continue reading)

Filip Stefaniak | 5 Mar 16:19 2004
Picon

gopher front

hello,
Im quite new to gopher.
Where I have to place a text which is shown before other links, like eg in 
gopherproject.org:
  THE GOPHER PROJECT
            ------------------

            Welcome to GOPHER!  Gopher is a slim, powerful, and
            fast way to present information in a hierarchial catalog online.
            Gopher actually predates the Web -- although most web browsers
            make excellent gopher browsers too.

            Good places to start are the "Why Gopher?" and "Using Gopher"
           areas!

and then links.

?

pozdrawiam,
filips

--

-- 
: jabber : filips@...
: Sluchaj dzieweczko! Ona nie slucha...
: zar z rozgrzanego jej brzucha bucha! 

John Goerzen | 5 Mar 18:11 2004

Re: gopher front

On Fri, Mar 05, 2004 at 04:19:18PM +0100, Filip Stefaniak wrote:
> hello,
> Im quite new to gopher.
> Where I have to place a text which is shown before other links, like eg in 
> gopherproject.org:

Hi Filip,

The answer depends on which gopher server you run.

With UMN gopherd (which is no longer suggested), you will have to add
files of type 'i' to your .names file.

With Bucktooth, you need to create a "gophermap" file and just add lines
of text.

With PyGopherd, you can do either the above, or you can create a file
named .abstract in directory and place the text in there.

-- John

>   THE GOPHER PROJECT
>             ------------------
> 
>             Welcome to GOPHER!  Gopher is a slim, powerful, and
>             fast way to present information in a hierarchial catalog online.
>             Gopher actually predates the Web -- although most web browsers
>             make excellent gopher browsers too.
> 
>             Good places to start are the "Why Gopher?" and "Using Gopher"
(Continue reading)

Filip Stefaniak | 5 Mar 19:05 2004
Picon

Re: gopher front

hello,
> > Where I have to place a text which is shown before other links, like eg in
> > gopherproject.org:

>With UMN gopherd (which is no longer suggested), you will have to add
>files of type 'i' to your .names file.

How should this file look like? Could you give me an example?
BTW, in manual for my gopherd, there is no such type as 'i'.

pozdrawiam,
filips

--

-- 
: jabber : filips@...
: Sluchaj dzieweczko! Ona nie slucha...
: zar z rozgrzanego jej brzucha bucha! 

Timm Murray | 13 Mar 16:58 2004
Picon

Announcing Gopher::Server 0.1 for Perl

The Gopher::Server 0.1 Perl module will soon be available on CPAN.  It 
implements the complete backend needed to create a Perl-based Gopher 
server.

The planned changes for 0.2 are to implement Gopher+, improve type 
detection (currently only detects plaintext, directories/menu entities, 
and considers everything else a binary file), and put in some actual 
documentation (ooohhh!)

This should be followed shortly with a ProtocolHandler for Apache2/mod_perl.

Alessandro Selli | 13 Mar 15:42 2004
Picon

Gopherd or pygopherd?

  Hello,
  	  I'm just now getting interested in Gopher and I'm currently running
a gopherd 3.0.3 server.  Since it's running on a slow machine (Sparc5-85),
would you recommend a C-compiled binary server like gopherd or do you think I
will not notice a big difference in system load/ memory consumption running
an interpreted server like pygopherd?  The server is not serving a community
and the Sparc5 is quite beefed up with ram (232MB).  Are there other
differences between those two that I should be aware of to choose the correct
server for my site?

  Bye,

  Sandro

--

-- 
Bellum se ipsum alet
       La guerra nutre se stessa

Livio, "Ab urbe condita", XXXIV,9

John Goerzen | 13 Mar 22:03 2004

Re: Gopherd or pygopherd?

On Sat, Mar 13, 2004 at 03:42:27PM +0100, Alessandro Selli wrote:
>   	  I'm just now getting interested in Gopher and I'm currently running
> a gopherd 3.0.3 server.  Since it's running on a slow machine (Sparc5-85),
> would you recommend a C-compiled binary server like gopherd or do you think I
> will not notice a big difference in system load/ memory consumption running
> an interpreted server like pygopherd?  The server is not serving a community
> and the Sparc5 is quite beefed up with ram (232MB).  Are there other
> differences between those two that I should be aware of to choose the correct
> server for my site?

Gopherd is no longer maintained.  Security holes were being found in it
on a regular basis, and nobody really had the inclination to give it a
thorough security audit given the fact that more advanced Gopher servers
existed.  Therefore, I would strongly urge you *NOT* to deploy UMN
Gopherd.

PyGopherd is, to a great extent, completely compatible with UMN Gopherd,
and in many cases, is a drop-in replacement for it.  Being written in
Python, it is immune to a whole class of security bugs that plague not
just Gopherd but other C-based servers as well.

You should have no problems at all running Pygopherd on that machine.
For a project such as a Gopher server, Python will not cause any
noticable performance changes.  You may be interested that some quite
high-capacity servers, such as the Zope web application server, are
written in Python and do not suffer performance problems.

There are several Gopher servers out there.  As the author of PyGopherd,
I may be biased here, but I'd say that PyGopherd is the most featureful
at present, due to its support for most features of both the UMN and
(Continue reading)

John Goerzen | 13 Mar 22:03 2004

Re: Announcing Gopher::Server 0.1 for Perl

On Sat, Mar 13, 2004 at 09:58:09AM -0600, Timm Murray wrote:
> The planned changes for 0.2 are to implement Gopher+, improve type 
> detection (currently only detects plaintext, directories/menu entities, 
> and considers everything else a binary file), and put in some actual 
> documentation (ooohhh!)

Nice.

> This should be followed shortly with a ProtocolHandler for Apache2/mod_perl.

And *that* will be Very Cool Indeed.

-- John

Vlad D. Markov | 14 Mar 00:11 2004

Re: Gopherd or pygopherd?

On Sat, 13 Mar 2004 15:03:11 -0600
John Goerzen <jgoerzen@...> wrote:

> On Sat, Mar 13, 2004 at 03:42:27PM +0100, Alessandro Selli wrote:
> >   	  I'm just now getting interested in Gopher and I'm currently
> >   	  running
> > a gopherd 3.0.3 server.  Since it's running on a slow machine
> > (Sparc5-85), would you recommend a C-compiled binary server like
> > gopherd or do you think I will not notice a big difference in system
> > load/ memory consumption running an interpreted server like
> > pygopherd?  The server is not serving a community and the Sparc5 is
> > quite beefed up with ram (232MB).  Are there other differences
> > between those two that I should be aware of to choose the correct
> > server for my site?
> 
> Gopherd is no longer maintained.  Security holes were being found in
> it on a regular basis, and nobody really had the inclination to give
> it a thorough security audit given the fact that more advanced Gopher
> servers existed.  Therefore, I would strongly urge you *NOT* to deploy
> UMN Gopherd.
> 
> PyGopherd is, to a great extent, completely compatible with UMN
> Gopherd, and in many cases, is a drop-in replacement for it.  Being
> written in Python, it is immune to a whole class of security bugs that
> plague not just Gopherd but other C-based servers as well.
> 
> You should have no problems at all running Pygopherd on that machine.
> For a project such as a Gopher server, Python will not cause any
> noticable performance changes.  You may be interested that some quite
> high-capacity servers, such as the Zope web application server, are
(Continue reading)


Gmane