I recently ran into a site with several modules, each of which was forwarding packets. The worst case was at a rate of 1 every 2 seconds or so.
The impact of communication layer latency is typically under estimated when trying to fix application performance problems but correct understanding is critical if you are to direct your efforts toward practical solutions.
TCP was designed to support end to end connections, that is, one host communicating directly with another host. Sure, there were bridges and routers in between, but those devices didn’t touch the TCP header or the payload.
When you contact customer support with a problem, the typical goal is to get it resolved FAST. I have observed that in many instances the initial contact with support coordination makes a fast resolution much less likely. This blog provides some tips to help speed up problem resolution.
Lots of people have created automated processes to transfer files using FTP. There are several different ways to do this, some better than others.
In my last blog I talked about automating file transfers using FTP. There are three issues with using FTP. First, your password is sent across the network in clear text making it available to anyone with a protocol analyzer.
Traceroute can be an invaluable tool when trying to diagnose connection problems to hosts on other networks. However to be used effectively you have to understand how it works and what the output means.
When writing a network application you can use non-blocking mode or blocking mode. Non blocking mode is more flexible and required when the application has to do multiple things, like servicing multiple sockets.
Thank goodness for regression tests. There I was, earlier this week, feeling really good about some new code that I had written and (I thought) debugged.
Over the years we have added a number of UNIX® features to VOS. One of the simplest and most useful of these is the ability to use dot (“.”) and dot-dot (“..”) as pathnames.