<div dir="ltr"><div><div>Erik Anderson:<br>
<br>> OK, brief networking stack lesson here.<br>
><br>
> IP, the basis for all of these technologies, is a Layer 3 protocol.<br>> TCP and UDP are both built on IP. They are Layer 4.<br>
> HTTP, SSH, SMTP, DNS, etc. are all built on TCP or UDP. They <br>> are Layer 7
(application) protocols.<br>
><br>
> So, when dealing with say HTTP, you're not *only* using HTTP, but >you're also using each level of the stack below that the protocol <br>> was built on. In
the case of HTTP, the stack goes something like <br>> HTTP/TCP/IP. For DNS, it's DNS/UDP/IP.<br>
><br>
<br></div>I'm aware of that. I guess this is a difference in terminology. <br>I think of UDT as replacing UDP in the application even <br>though UDT uses UDP.<br><br></div><div>Iirc, we previously discussed ssh tunnels and IPsec in <br>
</div><div>this newsgroup. As long as I keep using ssh tunnels, I'm<br></div><div>locked into using TCP. So using UDT rather than TCP <br>between my back and middle tiers isn't an option unless<br>I stop using ssh tunnels. I'm still thinking about using IPsec.<br>
</div><br><div><div>
> Excellent choice. I've been a die-hard apache fan for most of <br>> my sysadmin years, but have switched nearly every system <br>> I can over to nginx in the
last six months, and couldn't be happier.<br><br></div><div>That's good to hear. I started using nginx yesterday evening. <br><br></div><div>
-- <br><div dir="ltr">Brian Wood<br>Ebenezer Enterprises - so far G-d has helped us.<br><a href="http://webEbenezer.net" target="_blank">http://webEbenezer.net</a> (651) 251-9384<br><br><br><br></div>
</div></div></div>