DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=mHaMxUpjk7EH/kvq0GbP9+JJ9Pmc3NufWb8eN3WEtNQBWcCw1WqUBjiUE55E5kdnpq22wmVFy7H43qErUeTzLsu58hBvFpDbSK3w/caIWv+tZXqetr9z9PqeMI0IQlFpBDYoF/NSZXeQlfJOY9s12rv7tbR1Pu1/Op12pp0QDLk=
  ;
Message-ID: <20060817173342.76707.qmail@web35507.mail.mud.yahoo.com>
Date: Thu, 17 Aug 2006 10:33:42 -0700 (PDT)
From: JumpJet Mailbox <jumpjetinfo@yahoo.com>
Subject: [gopher] Re: Active ?
To: gopher@complete.org
In-Reply-To: <f705f7020608171000m1789a3c1r4f2c74e98375eaf2@mail.gmail.com>
MIME-Version: 1.0
Content-type: text/plain
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

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 you), 
  3) Switch to a different Gopher Client (may require changing operating systems).  
   
  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@gmail.com> wrote:
  On 8/17/06, JumpJet Mailbox wrote:
>
> Neither gopher://alessandro.route-add.net or gopher://gopher.rp.spb.su 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://alessandro.route-add.net it is 192.182.210.150, and the case of gopher://gopher.rp.spb.su it is 81.3.164.16 ), 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.