delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/08/04/22:49:02

From: Hyper <jimb AT snip DOT net>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: I am absolutely new to programming
Date: Wed, 04 Aug 1999 06:54:56 -0400
Organization: None, very disorganized
Lines: 34
Message-ID: <37A81C00.DB3D9C7@snip.net>
References: <iSop3.127$m67 DOT 289214 AT news DOT bctel DOT net> <7o5pin$t74 AT dfw-ixnews10 DOT ix DOT netcom DOT com> <37A691B3 DOT EC8F8936 AT snip DOT net> <37A7EBF3 DOT 91958FF2 AT megsinet DOT net>
NNTP-Posting-Host: harc2a64.snip.net
Mime-Version: 1.0
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

David Oppenheimer wrote:
> 
> Please note that hyperlinks are governed by a host to host protocol called UDP
> or User Datagram Protocol which is very unreliable and has zero error checking
> (kinda like sending off a postcard onto the WWW with the message "I am looking
> for remote server 217.64.76.93". There is no two way communication, no virtual
> circuit, no sequencing, no reliability).  It is quite quick and requires much
> less CPU overhead, but lacks some of the advantages of TCP or Transmission
> Control Protocol - a host to host protocol used for downloading files.  (TCP
> has error checking, sequencing, acknowledgments, and is very reliable.  It is
> comparable to a phone call where you might say "Are you there?" "Yes I'm
> here." " I am ready to send you some information"  "I am ready to receive it"
> "Did you get the information I just sent?" etc. etc. etc.)
> 
> Before jumping to the conclusion that a hyperlink is bad, or that a server on
> the WWW is down, you need to try a hyperlink at least several times due to the
> inherent unreliability of the UDP protocol.
> 
ok then, let me rephrase my opinion.  I clicked the link, "Netscape is unable to
find the server www.swcp.com" So i typed the address "http://www.swcp.com" and
hit enter, same message.  I pinged "www.swcp.com" with ping.exe, couldn't find
host www.swcp.com.  Perhaps my ISP's DNS server for some odd reason didn't have
it listed, maybe there was a problem causing the DNS server to go down, i don't
know.  What i do know is that after trying for about 15 minutes, checking stuff
like scwp.com, swpc.com, wspc.com, and wscp.com and not finding the site that
was refered, i posted a message stating that the link was bad. As for your
little explanation of the difference between UDP and TCP, thanks, but i knew all
that already.  None of that would explain how 30+ tries to find a server come
back bad though
-- 
My heart goes out to the families of Gene Hart and Dimitri Tertyshny
Who both died tragically during the month of July, in two seperate instances
May both of your souls rest in peace
Personal page -- http://members.xoom.com/Hyper_Hands/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019