Remoting TCP vs HTTP

  • Thread starter Thread starter techy
  • Start date Start date
T

techy

hi guys i want to discuss about pro and cons of using tcp in remoting
and i would like to see if all techies share their practical experience
on this group


thanks in advance
 
It would be hard to use HTTP without it.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Chicken Salad Alchemist

A lifetime is made up of
Lots of short moments.
 
Hello techy,

In 2 words - Performance is higher in TCP
See there http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/bdadotnetarch14.asp

t> hi guys i want to discuss about pro and cons of using tcp in
t> remoting and i would like to see if all techies share their practical
t> experience on this group
t>
t> thanks in advance
t>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
 
so what is the status of tcp with firewalls

i mean during vpn stuff

if some on tries connecting vpn is tcp goood\
 
Firewalls block TCP/UDP Ports. Port 80 is the HTTP port, and is almost
always left open. Ports 21 and 25 are for FTP and SMTP respectively, and are
also usually left open by Firewalls. However, almost any other Port must be
opened exclusively to use. In other words, it's not a matter of how good TCP
is; it's almost the only game in town these days. HTTP, SMTP, FTP, and just
about everything else except for UDP, are carried over TCP. What really
matters in any network communication, remoting or otherwise, it what Ports
are opened, and what Ports are not. There are 65, 536 of them on any
machine. A good Firewall blocks about 65, 530 of them, more or less.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Chicken Salad Alchemist

A lifetime is made up of
Lots of short moments.
 
Back
Top