Welcome to outblasts.com

Web Hosting - Redundancy and Failover Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad. Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily. Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams. A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'. A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path. Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy. That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place. And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later. One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem. Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine. The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience.

Web Hosting - FTP and Other File Transfer Tools Anything related to the Internet or computers is bound to introduce technical issues pretty soon. One of the earliest that novice web site owners encounter is FTP, which is an acronym for File Transfer Protocol. Seeing it spelled out, it's easy to see why those in the know quickly move to speaking in short hand. The reason web site owners soon will (or need to) become familiar with FTP is obvious to anyone who has built a site on a remote server. You have to have some way of getting the files to the remote computer and FTP is one of the most common tools. It's also one of the simplest and most efficient. FTP is composed of two parts: the client software and the server software. It's similar, in a way, to talking to someone on the phone who writes down everything you say. You (the client) make a request ('transfer this file to the server') and the listener (the server) takes the request and acts on it. That request to copy a file from a local computer to the remote one is carried out (often 'under the covers') by a PUT command, as in PUT this there. You create the web page (in the form of a file) and then PUT the file on the server. To move a file in the opposite direction, from the remote server to your local computer, your client software issues a GET command. Many FTP clients have graphical interfaces, similar to Windows Explorer, that allow you to drag-and-drop or otherwise copy the file without ever seeing the actual commands that carry it out. But it's helpful sometimes to know what goes on underneath. In tricky cases it can be an advantage to use a command line interface (in Windows, the 'DOS box', with a similar interface familiar to most Linux users). Knowing the commands and being able to use them in the command line form can sometimes help you diagnose what is going on when the graphical tools misbehave. But FTP is not the only way to get a file from here to there. In fact, your browser moves files around from a remote computer to your local one all the time. In most cases, when you type in or click on a URL, what happens under the covers is in essence a file transfer process. The web page is transferred from the web server to your local computer then displayed by the browser. Alternatively, you can sometimes even email a web page/file from your local computer to the remote server, then use an email client on the server itself to get the file and put it in a folder. That requires that you have some form of access to the remote computer. But there are many ways of doing that, such as in-built utilities in the operating system or using commercial remote control programs. Those alternatives can be helpful to know in cases where the FTP file transfer process is misbehaving. Having more than one way to accomplish the task helps you diagnose what might be going wrong. It also helps you get the job done when the usual tools aren't cooperating. The more you learn about these sometimes puzzling acronyms, the easier you can accomplish your own goals.

The Ins and Outs of Free Writing Contests (free writing contests) Free writing contests are available by the thousands. They are virtually a dime a dozen on the Internet. No matter what your niche is in the writing community there is a free writing contests out there for you. How do you know which ones to enter and which ones are legitimate? That’s simple. You do what you do best-- research. While providing the story for the free writing contest will probably be the easy part, researching the thousands of available contests will be a daunting task. If this is un-chartered water for you, you have the start at the beginning. Finding what free writing contests are available. Grab a notebook or start a word document and list the contests that are available. Beside each contest name you will want to put what kind of writing they are looking for and when it needs to be done by. By doing this first you will be able to eliminate any that do not coincide with your writing niche or with your schedule. Now the free writing contest research begins. Finding out if a contest is worthwhile and legitimate is comparable to running a background check on a person. First check the contest website. Do they have all contact information available? Do they tell you what company is hosting the contest? If they are not, you will have likely found warning number one that it is a scam. So scratch those off your list or at least move them to the bottom until you can find out more information on them. Start asking around to colleagues and writers groups. Search the writing forums and the Internet scam sites. The Better Business Bureau is also a good place to look. Once you narrowed the free writing contests down to the legitimate ones, read the contest rules and regulations. Some contests require you signing over all rights to a story even if you don’t win. Are you willing to do this? Giving up rights to you writing is a lot easier to do when you are getting something in return. After you enter there is no going back, so make sure this is what you want to do. The final thing you need to look for is if the contest is just a cover up to get you to buy services or products. This does not necessarily mean they are a scam or don’t actually award winners. It simply means that they will try to entice you to use their critiquing services or offer you a book at a reduced fee that your work will be published in. Being published sounds like a great deal but is it a book that carries prestige that people are going to see? Many authors think that writing contests will launch their career into a successful endeavor. This is not the case, especially for free writing contests. Even winning the grand prize of a smaller known contest is not going to affect your literary journey. Even though they may not springboard your career, there are good reasons to join writing contests. You will get unbiased opinions and valuable feedback from the judges. If you make it into the higher rounds, editors could also see your writing. Ultimately whether you enter a free writing contest the choice is yours. Just ask you self if the time spent writing and researching the piece you choose to enter is worth writing for free in most cases. The critique and feedback may be the most worthwhile thing you receive from the contest. But then again the judges opinions are a dime a dozen just like the contests.