Complete.Org: Mailing Lists: Archives: gopher: August 2006:
[gopher] Re: Active ?

[gopher] Re: Active ?

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Active ?
From: JumpJet Mailbox <jumpjetinfo@xxxxxxxxx>
Date: Thu, 17 Aug 2006 10:33:42 -0700 (PDT)
Reply-to: gopher@xxxxxxxxxxxx

ALL available Gopher Clients are buggy (sorry).  This is primarily due to the 
majority of Gopher Clients being abandoned by their authors.  Unfortunately 
your only options in most cases are:
  1) Contact the Client developer and ask them to address the problem,
  2) Modify the software yourself to fix the bug (or hire someone to do it for 
  3) Switch to a different Gopher Client (may require changing operating 
  Note that different software handles transactions differently (one may wait 
until it gets a response from a server before it allows user interverntion, 
while another lets the user intervene at any time).  None of the staff at 
JumpJet work with Unix-like software at this time, so we are currently unable 
to test this Client ourselves.  Perhaps someone else reading this thread could 
take up the cause?  
Stegozor <stegozor@xxxxxxxxx> wrote:
  On 8/17/06, JumpJet Mailbox wrote:
> Neither gopher:// or gopher:// are 
> accessable from Port 70. This is probably due to these Gopher servers being 
> removed from Internet service.
> The error you are experiencing appears to NOT be a issue with your Gopher 
> software, but an issue with your DNS server. As you state:
> "When I go to a site I get mixed messages on unreachable links, one is pretty 
> instantaneous telling me that the site is not available, the second hangs the 
> gopher program for 2-3 minutes before telling me that it cannot connect to 
> the host.".
> The "instantaneous" failure is because there is no longer a physical IP 
> address associated with the server you are trying to reach, so the DNS server 
> sends back a quick response. The failure that APPEARS to "hang" is because 
> there is still an IP address associated with the unreachable servers (in the 
> case of gopher:// it is, and the case 
> of gopher:// it is ), and the DNS server spends a 
> considerable amount of time trying to reach the associated pysical IP address.

Thanks for the explanation, but there's something I still don't
understand and that seems to be a bug in Gopher client to me: when I
press control-c during an attempt to contact these servers, I can't
take back the control of the program, the beep (from the buzzer)
becomes weird and repetitive and I have to close the terminal window.
I tried the same links with SeaMonkey, simply pressing escape stops
the transaction.

Do you Yahoo!?
 Everyone is raving about the  all-new Yahoo! Mail Beta.

[Prev in Thread] Current Thread [Next in Thread]