HighTechTalks DotNet Forums  

Re: Big perfornance problem with HTTP requests

Dotnet Framework (Performance) microsoft.public.dotnet.framework.performance


Discuss Re: Big perfornance problem with HTTP requests in the Dotnet Framework (Performance) forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
jeremiah johnson
 
Posts: n/a

Default Re: Big perfornance problem with HTTP requests - 04-24-2006 , 06:47 AM






Vadym Stetsyak wrote:
Quote:
You're using HTTP over TCP. TCP protocol doesn't support broadcasting.

?? Yes it does...

If your subnet is 10.10.10.*, then that subnet's broadcast address is
10.10.10.255.


Reply With Quote
  #2  
Old   
jeremiah johnson
 
Posts: n/a

Default Re: Big perfornance problem with HTTP requests - 04-24-2006 , 06:54 AM






Actually you're right, TCP doesn't define broadcasting, IP does, because
IP defines addressing. TCP is a transmission protocol, IP is the
addressing protocol.

So yeah, neither UDP or TCP support broadcasting, its IP that supports it.

But if you're trying to say that you can't send a TCP message to a
broadcast address, you're wrong. Back in the day before broadcast
floods were common, could ping the .255 address on your network and
watch dozens and dozens of ping responses come back. Nowadays broadcast
addresses don't make it through routers at all.

jeremiah

jeremiah johnson wrote:
Quote:
Vadym Stetsyak wrote:

You're using HTTP over TCP. TCP protocol doesn't support broadcasting.


?? Yes it does...

If your subnet is 10.10.10.*, then that subnet's broadcast address is
10.10.10.255.

Reply With Quote
  #3  
Old   
Vadym Stetsyak
 
Posts: n/a

Default Re: Big perfornance problem with HTTP requests - 04-24-2006 , 07:13 AM



Hello, jeremiah!

jj> But if you're trying to say that you can't send a TCP message to a
jj> broadcast address, you're wrong. Back in the day before broadcast
jj> floods were common, could ping the .255 address on your network and
jj> watch dozens and dozens of ping responses come back. Nowadays
jj> broadcast addresses don't make it through routers at all.

ICMP is not TCP. Yes you can send connection request to broadcast address, but connection is an atomic thing you cannot maintain broadcast connection, so trying to connect to "xxx.xxx.xxx.255" doesn't make sense.

.NET sockets ( stream socket -> tcp socket ) will not allow you to perform connection attempt on this address.

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.