[gopher] Re: Gopher+ Suggestion
[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
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@xxxxxxxxxxxx> GPG: 0x8A1D9A1F www.complete.org
- [gopher] Re: Gopher+ Suggestion,
John Goerzen <=
|
|