Another reader asks:
What is the difference between an IP datagram and a TCP segment?
Mostly, its terminology used in the standards documentation, though upon transmission a TCP segment gets created first from the application layer data and an IP datagram contains the TCP segment in the payload section of the IP datagram. I’ve got lots of tutorials on these subjects in this website.
I was so focused on getting the new layout online and getting the blog up and running that I realized I had forgotten to put the donate link back into the design–several of you mentioned it was missing. So, a little HTML code and some work in a graphics application later, the form is back online.
What do donations to InetDaemon.Com support? Donations offset the costs of operating the web server, the website and domain name services, all of which cost money. Please consider supporting InetDaemon.Com with your generous donations. I’m looking into adding a forum, podcasts, webcasts and online seminars, as soon as I can put together all the right resources.
Keep checking back!
Many years ago, I created an online form (Ask InetDaemon) through which my loyal and curious readers can send me an e-mail with a question about a tutorial or other subjects. Replying to the e-mail helped the person who sent me the e-mail, but the questions are often quite good and serve as a great basis of writing a tutorial, but unless I wrote a tutorial page, there was no way to share it with my readers.
Now that I have a blog, I can actually reply to these e-mails in a more public forum where they will help more than just one person. The “Ask InetDaemon” category will contain those answers. Subscribe to the RSS feed for the category to see new questions and my answers.
The “Ask InetDaemon” blog category will be reserved for the e-mails I answer. I’m going to try to answer one question every two weeks on Friday evenings for your Saturday morning amusement.
However, you have to do your part:
First, you have to send me some real questions via the online form. I don’t promise to answer them all and I can’t do your school work for you.
Second, if you want to comment on my responses to any of the e-mails in this category, you need to register for a free InetDaemon.Com account. Only registered members can comment on my posts.
Stay Tuned!
I’m going back through the articles I’ve written and saved, but never published, so some articles are going to pop up as I approve them (click the publish button). Not sure why I was so cautious in only saving them instead of publishing them. Too shy? Maybe. Maybe just a little paranoid.
In any case, expect quite a few ‘new’ old articles to pop up soon.
P.S.
Don’t forget to register for a free account. Accounts are free (no charge, no cost). Only registered users can add comments (reply) to my blog postings. I’m looking at adding a forum to the site and in order to block the spammers from posting comment-spam to my blog or to the forum, I have to have a list of ‘permitted’ users, and that means asking my readers to register. It’s simple, quick and relatively painless.
Thanks!
Click here to Register for a free account.
I need to lock out spammers and other bad elements so that your use of the site is as problem-free as possible. Please register sooner, rather than later.
I have long desired to have an interactive website instead of a set of flat, static web pages. To that end, I recently installed WordPress to handle the blogging. I’ve always wanted to allow my readers to respond to the articles I write with their own questions so that others can read them and learn from the answers I provide. Good questions often force me to take a second look at an article or tutorial from a different perspective, which often results in a better explanation of the topic and a better tutorial overall.
I’m also looking into podcasting and investigating other applications to provide interactive functionality such as polls and community based functions such as forums, bulletin boards, etc.
The problem is, hackers and spammers like interactive websites. They post junk links, or disguise hacker-sites as helpful or interesting links. To keep out those bad elements, I’ll have to lock them out by only permitting people who have an account.
Again, when you register, the account is free, I just have to lock the undesirable hackers and spammers out. The good news is that every response will be reviewed and approved by InetDaemon personally, guaranteeing that nobody sees any spam (well, hopefully nobody).
Thanks to all my loyal readers and keep checking back for more updates and changes to the site!
–InetDaemon
Servers are computers that host services. One type of server is a web server. When developing a website, it is often handy to have a second web server on which you can test new ideas without causing the real website (the production site) to crash or have problems. This second server is called a ‘development’ server.
I recently finished setting up a development web server to host WordPress. I already had a development web server with a copy of my website’s static web pages at home. I use this development web server to test out ideas for the layout and design of the InetDaemon.Com website. I also use the development server to test Server Side Includes and new Perl scripts without breaking the live website you’re currently reading in your web browser.
My ‘production’ website has hundreds of static web pages (the Tutorials), which are served by an Apache web server running on a UNIX based computer. The rest of my website is the blog, which is handled by WordPress, a PHP-based CGI application that dynamically loads content from a MySQL database and turns it into dynamic web pages. If the name of the web page you’re reading ends in .php, it’s a safe bet it’s being rendered by WordPress.
My development web server is a Microsoft IIS web server running on Windows XP, which makes it a very different platform from my live site. Why did I choose IIS for the local server? Simply for the challenge. Since I already had IIS running, and I had also configured it to have a cgi-bin folder where I test out my Perl scripts I figured it wouldn’t be too much of a stretch to get a WordPress site up and running on it. Getting my local IIS web server running was simple. Getting WordPress running took just a little extra work.
First, to run WordPress on a Microsoft IIS server, you must have IIS installed before you install anything else. Next I installed MySQL, a database server application. Next, I downloaded the latest version of PHP (the script engine that parses the PHP language that WordPress is written in). I installed PHP with ISAPI option for IIS and the MySQL extensions enabled. Finally, I downloaded the latest version of WordPress, copied it to the same folder location on my local webserver as it is on my public website and then ran the WordPress install.
That’s all it took.
Now I have a server at home that delivers exactly the same pages as the production InetDaemon.Com website, looks the same and feels the same when you browse it, but has IIS as the web server instead of Apache.
If I ever get around to writing up a more specific set of steps, I’ll post it online as a tutorial.