Welcome to www.taxkingsandqueens.com

Freebie Etiquette (Yes, There is Such a Thing!) When you are on the hunt for free stuff, it can be easy to be so blinded by the offers that your manners go flying out the window completely. You may also just not realize that when it comes to taking advantage of freebies there is a general code of conduct that it pays to follow. While you are racking up the free stuff, keep these common courtesy rules in mind so that you are doing your part to keep the hunt for freebies fun and enjoyable. Freebie etiquette rule number one is to remember that there is a face behind every freebie, no matter how distant it may seem. Since so many freebies come from websites and you don’t actually have interaction with a human being while you are getting them, it can be very easy to forget that someone (or very likely, a lot of someones) worked hard to bring you that website and that free deal. If you have a problem with a website or a form while trying to get some free stuff, deal with it as respectfully as you would if you had to approach a customer service rep in person. Leaving foul-mouthed posts on a message board or unloading a barrage of outrage on a customer reply form isn’t the way forward. Someone – a real person – will have to help you, and you’ll get a lot further by treating them with respect. Respect is also the name of the game when it comes to rules attached for freebie offers. There are often restrictions in place for taking advantage of free offers, such as the age you have to be to cash in on the offer or how many offers per household can be taken. Sure, there are plenty of ways to get around these rules and “trick” a company into giving you an offer for which you are not really eligible. However, when you try to simply bleed out as many free offers as you can, you’re only making it hard on companies to be able to keep bringing these offers to you. If this freebie isn’t for you, take a back seat and make room for the folks who can take advantage of it. Your time will come. Related to this last rule is the idea of not being too greedy when gobbling up the free stuff. Just because something is free doesn’t mean you should use a “smash and grab” approach and go for as much as you can get of anything you can get. Remember that there are a lot of other people out there who like to get in on the freebies, too, and think about how you would feel if you lost out on something you really wanted because someone came along and took them all. Don’t take more than your share of any free offer, and don’t take things you don’t want or need just because they’re free. Everyone loses when you do that. Last but not least, if you have an opportunity to say thanks for a freebie, grab it. Of course, this can be hard to do when the free offers you are taking advantage of are found on the Internet, but there are still ways. Look for the customer comment field in the request forms you fill out to get your free stuff and leave a quick thank you there. You can also write a thank you on message boards and chat rooms that are associated with the freebie websites. The good will generated by your gratitude will only help convince companies that freebie offers are useful tools for reeling in the customers.

Web Hosting - The Internet and How It Works In one sense, detailing the statement in the title would require at least a book. In another sense, it can't be fully explained at all, since there's no central authority that designs or implements the highly distributed entity called The Internet. But the basics can certainly be outlined, simply and briefly. And it's in the interest of any novice web site owner to have some idea of how their tree fits into that gigantic forest, full of complex paths, that is called the Internet. The analogy to a forest is not far off. Every computer is a single plant, sometimes a little bush sometimes a mighty tree. A percentage, to be sure, are weeds we could do without. In networking terminology, the individual plants are called 'nodes' and each one has a domain name and IP address. Connecting those nodes are paths. The Internet, taken in total, is just the collection of all those plants and the pieces that allow for their interconnections - all the nodes and the paths between them. Servers and clients (desktop computers, laptops, PDAs, cell phones and more) make up the most visible parts of the Internet. They store information and programs that make the data accessible. But behind the scenes there are vitally important components - both hardware and software - that make the entire mesh possible and useful. Though there's no single central authority, database, or computer that creates the World Wide Web, it's nonetheless true that not all computers are equal. There is a hierarchy. That hierarchy starts with a tree with many branches: the domain system. Designators like .com, .net, .org, and so forth are familiar to everyone now. Those basic names are stored inside a relatively small number of specialized systems maintained by a few non-profit organizations. They form something called the TLD, the Top Level Domains. From there, company networks and others form what are called the Second Level Domains, such as Microsoft.com. That's further sub-divided into www.Microsoft.com which is, technically, a sub-domain but is sometimes mis-named 'a host' or a domain. A host is the name for one specific computer. That host name may or may not be, for example, 'www' and usually isn't. The domain is the name without the 'www' in front. Finally, at the bottom of the pyramid, are the individual hosts (usually servers) that provide actual information and the means to share it. Those hosts (along with other hardware and software that enable communication, such as routers) form a network. The set of all those networks taken together is the physical aspect of the Internet. There are less obvious aspects, too, that are essential. When you click on a URL (Uniform Resource Locator, such as http://www.microsoft.com) on a web page, your browser sends a request through the Internet to connect and get data. That request, and the data that is returned from the request, is divided up into packets (chunks of data wrapped in routing and control information). That's one of the reasons you will often see your web page getting painted on the screen one section at a time. When the packets take too long to get where they're supposed to go, that's a 'timeout'. Suppose you request a set of names that are stored in a database. Those names, let's suppose get stored in order. But the packets they get shoved into for delivery can arrive at your computer in any order. They're then reassembled and displayed. All those packets can be directed to the proper place because they're associated with a specified IP address, a numeric identifier that designates a host (a computer that 'hosts' data). But those numbers are hard to remember and work with, so names are layered on top, the so-called domain names we started out discussing. Imagine the postal system (the Internet). Each home (domain name) has an address (IP address). Those who live in them (programs) send and receive letters (packets). The letters contain news (database data, email messages, images) that's of interest to the residents. The Internet is very much the same.

Web Hosting - Bandwidth and Server Load, What's That? Two key performance metrics will impact every web site owner sooner or later: bandwidth and server load. Bandwidth is the amount of network capacity available, and the term actually covers two different aspects. 'Bandwidth' can meanthe measure of network capacity for web traffic back and forth at a given time. Or, it sometimes is used to mean the amount that is allowed for some interval, such as one month. Both are important. As files are transferred, emails sent and received, and web pages accessed, network bandwidth is being used. If you want to send water through a pipe, you have to have a pipe. Those pipes can vary in size and the amount of water going through them at any time can also vary. Total monthly bandwidth is a cap that hosting companies place on sites in order to share fairly a limited resource. Companies monitor sites in order to keep one site from accidentally or deliberately consuming all the network capacity. Similar considerations apply to instantaneous bandwidth, though companies usually have such large network 'pipes' that it's much less common for heavy use by one user to be a problem. Server load is a more generic concept. It often refers, in more technical discussions, solely to CPU utilization. The CPU (central processing unit) is the component in a computer that processes instructions from programs, ordering memory to be used a certain way, moving files from one place to the next and more. Every function you perform consumes some CPU and its role is so central (hence the name) that it has come to be used as a synonym for the computer itself. People point to their case and say 'That is the CPU'. But, the computer actually has memory, disk drive(s) and several other features required in order to do its job. Server load refers, in more general circumstances, to the amount of use of each of those other components in total. Disk drives can be busy fetching files which they do in pieces, which are then assembled in memory and presented on the monitor, all controlled by instructions managed by the CPU. Memory capacity is limited. It's often the case that not all programs can use as much as they need at the same time. Special operating system routines control who gets how much, when and for how long, sharing the total 'pool' among competing processes. So, how 'loaded' the server is at any given time or over time is a matter of how heavily used any one, or all, of these components are. Why should you care? Because every web site owner will want to understand why a server becomes slow or unresponsive, and be able to optimize their use of it. When you share a server with other sites, which is extremely common, the traffic other sites receive creates load on the server that can affect your site. There's a limited amount you can do to influence that situation. But if you're aware of it, you can request the company move you to a less heavily loaded server. Or, if the other site (which you generally have no visibility to) is misbehaving, it's possible to get them moved or banned. But when you have a dedicated server, you have much more control over load issues. You can optimize your own site's HTML pages and programs, tune a database and carry out other activities that maximize throughput. Your users will see that as quicker page accesses and a more enjoyable user experience.