Home

 


Re: Client doesn't drop failed source Posted on: Wed, 20 Jan 2010 05:07:59 GMT

Rick Jones wrote:
> David Woolley wrote:
>> For a start, if it dropped a source on the first missing reply it
>> would result in clock hopping, which is undesirable. UDP is
>> unrliable, and you cannot rely on getting every query returned.
>
> In that sense then, even TCP is unreliable for it cannot guarantee
> getting every query returned. What distinguishes TCP from UDP is that
> TCP will make multiple attempts to deliver the data and then signal
> the probable (but not certain) non-delivery of data.
>
> rick jones

More importantly, TCP requires a 3-way handshake before it can deliver
the packet, so there is setup time, delivery and tear-down time involved
as well just to deliver one small packet.

Danny

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
56522. Re: Client doesn't drop failed source
56523. Re: Client doesn't drop failed source
56524. Re: Client doesn't drop failed source
56525. Re: Client doesn't drop failed source
56526. Re: Client doesn't drop failed source
56527. Re: Client doesn't drop failed source
56528. Re: Client doesn't drop failed source
56529. Re: Client doesn't drop failed source
56530. Re: Client doesn't drop failed source
56531. Re: Client doesn't drop failed source
56532. Re: Client doesn't drop failed source
56533. Re: Client doesn't drop failed source
56534. Re: Client doesn't drop failed source
56535. Re: Client doesn't drop failed source
56536. Re: Client doesn't drop failed source
56537. Re: Client doesn't drop failed source
56538. Re: Client doesn't drop failed source
56539. Re: Client doesn't drop failed source
56540. Re: Client doesn't drop failed source
56541. Re: Client doesn't drop failed source