Time for another question from my Ask InetDaemon mailbox:
Thanks for the excellent article on TCP, this was the best ever explanation I've found. Could you please provide me with the C++ implementation code for TCP handshake protocol?The handshaking is a function of the TCP protocol, and not really a protocol unto itself. Thus, handshaking is not a standalone piece of code. It’s integrated in the actual TCP software, first implemented in Berkeley BSD UNIX.
If you want a copy of the source code, you should learn to use a CVS client to download (sync) a copy of the BSD source in the CVS repository, provided you’re using a BSD compatible computer and operating system. The Berkeley Sockets implementation is the de-facto standard for TCP.
See:
Synchronizing Your Source.–InetDaemon
“Let’s just hope we don’t have a burnout.” — Han Solo, Star Wars – The Empire Strikes Back
Just reconfigured the site to roll out the new blogging software. Took a few minutes to get the links and the CSS lined up and fixed, but it looks pretty good so far. Let me know if you see any problems and add a reply or two to tell me what you think of the website’s new design.
InetDaemon.Com has moved from Gate.Com to BlueHost.com. Changing providers always entails a few glitches, but it appears that this has gone fairly seamlessly. I’m already getting hits at the new IP address.
Please bear with me while I work to resolve any issues related to transitioning to the new site.
One of the issues that you have when transferring a domain is that you have to set up new mail accounts. As soon as the new internal mail accounts are online, and mail is flowing, I’ll be able to receive, and respond, to your e-mails.
If you are reading this page, InetDaemon.Com has officially moved from Gate.com to Bluehost.com. If you have a Gate.Com or Hostsave.Com account, we highly recommend you move to another provider.
I created my account at BlueHost today, uploaded the files and made some quick configurations at BlueHost. Next, I changed my DNS where I registered my domain and voila’! InetDaemon.Com is up and running at the new hosting provider without a hitch (as far as I can tell). Now to deal with those pesky e-mail accounts everyone seems to think is so important.
Put simply, Gate.Com’s MySQL configuration won’t support one copy of WordPress being accessed by one person. Since I’m a geek, I know how to access the configuration settings for MySQL directly. Gate uses a single MySQL database instance which is only configured to allow 1500 total connections across their entire customer base. Furthermore, their configuration allows abandoned sessions to remain active for 8 hours, further reducing the availability of the database.
These restrictions prevent applications such as WordPress and eCommerce applications from functioning.
The key to a mostly seamless move of your domain from one hosting provider to another is preparation.
You must set up your future home, verify it is operational, then change where your registrar’s DNS points. Many years ago, I registered the InetDaemon.Com name, and then found a hosting provider. Back then, hosting providers didn’t do Domain Name registration, so today, moving my domain is a snap.
Today’s hosting providers won’t let you pry your own domain out of their cold, dead hands without at least some dynamite and a steam shovel. That’s why you register your domain yourself with a registrar and then find a hosting provider. That way, all you have to do is change the DNS pointer at your registrar. Moving a domain from one registrar to another is a painful experience and makes for messy transitions, so when your web hosting provider IS your registrar, it gets messy.
Because I use a registrar that is separate from my hosting provider, it took less than two hours to do the complete move.