Date: Sun, 21 Jul 2002 21:08:12 -0500
From: John Goerzen <jgoerzen@complete.org>
To: gopher@complete.org, rcooley@myrealbox.com
Subject: [gopher] Re: Gopher+ Suggestion
Message-ID: <20020722020812.GD1410@complete.org>
References: <3D396734.4070409@myrealbox.com>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3D396734.4070409@myrealbox.com>
User-Agent: Mutt/1.4i
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


On Sat, Jul 20, 2002 at 06:35:48AM -0700, R. Cooley wrote:

> My single problem with gopher, is that the hostname and ports are 
> static.  So, if I am running gopherd on a private network, and making 
> the gopherd port available to the outside, both the hostname and the 
> port must be the same on the private network, as well as ouside the 
> private network.  This is often not the case.  In fact, that is the very 
> issue keeping me from running a gopher server.

Hmm, I'm not quite sure I follow you.  Gopher selectors do indeed support
specifying a port.  If you run a gopherd on, say, port 2280, you can specify
port 2280 in the selectors.  If on the inside it shows up as 2270, you could
just run a second gopherd instance for the inside, making sure to say Port=+
in your .Links files.

Other than that, I'm not sure that this is a problem different than HTTP
servers face?  Perhaps I'm missing something here.

Thanks,
John

-- 
John Goerzen <jgoerzen@complete.org>    GPG: 0x8A1D9A1F    www.complete.org