Welcome to www.msunderestimated.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.

“To-may-to” “To-mah-to” Does it Matter How You Say it? (second language writing articles) Is it possible for anyone to be a writer? In the United States, it’s easy to believe that anyone can to anything until you start looking more closely at the issues. Not everyone is equipped to be successful. There may be some individuals without any personal wealth that can get scholarships for higher education and therefore enter into better paying jobs. Some might not make it though. When it comes to language, it becomes a big deal sometimes how you talk based on where you live. Writing is the same way. If there is a standard language, it can be very difficult to break into the writing world with less than perfect abilities in that language. If English is your second language, writing articles is still a possibility. The Changing Population and Standardized Language In the United States, the vast majority of the population speaks what is called Standard English. That means that they speak in an agreed upon system of rules and acceptable words. There are many native English speakers that may speak a dialect other than Standard English, but they are able to switch into the most acceptable dialect when the situation calls for it. There are increasing numbers of non-native English speakers in the country though. While there are occasional battles about making some other language acceptable, Standard English continues to win out. The desire is for continuity and a united nation. What that means for non-native speakers is that many job opportunities may not be opportunities. If English is your second language, writing articles may not seem like an option for you. There are some possibilities out there though. Hiring an Editor It is definitely possible for English as a second language writing articles to become acceptable for Standard English publications. Individuals may be able to learn well enough to be able to write well for standard publications. If not, and if the writing is still engaging and good, you may want to hire an editor. You can hire one locally or freelance to help you with your wording so that it fits into a publication’s style and tone. In all reality, even first language English speakers can use the help of an editor in this way. As a second language learner, you will just require different talents from an editor. By employing an expert, you can get your second language writing articles published anywhere that publications are printing. First Language Article Options Standard English publications are not the only ones printing in the United States. Even though there is a push to unify the language all over the country, there is a definite need for publications in other languages. As mentioned earlier, the population is changing. There are increasing numbers of non-native English speakers that live in this country. Many of the people may not speak any English at all. Those people create a market for printed material in their own language. A talented writer who is a native speaker can do a great job in writing articles in their own language. Many publications are also translated which is another interesting job opportunity. If English is your second language, writing articles for various publications is still an option. You can learn to write Standard English, but you don’t necessarily have to. A good editor can turn your writing into something that would be appreciated all over the country. You can also find opportunities writing for those who speak your native language. Language does not have to be a barrier. If anything, communication is getting better and better all the time. You can be a part of the process by writing articles in English or otherwise. In addition to your language skills, you have extensive cultural knowledge that others need to know.

How to copyright software How to Copyright Software Sanely If you're wondering how to copyright software the good news is you've probably already done it. At least you have if you have ever written software. Most people however get confused over exactly what having a copyright for their software means and this is the trickier question to answer. First of all, thinking it isn't going to do it and you can't really copyright the things you think. Second, only those things that can be seen (when it comes to software) can be copyrighted. If you want to protect the abstract, look into patents. Otherwise if it is original, fixed, and tangible you can copyright it. Essentially you already know how to copyright software if you've put it into a finished form. Once you've written the source code the copyright belongs to you. Copyrighting software doesn't offer the protection that many people hope it will. The idea of the software and anything about the finished product that wasn't available in a tangible (visible) form isn't protected by the copyright. In fact the only thing that is undeniably protected by copyright when it comes to software is the source code. The question you should be asking is now how to copyright software, it is how to patent your software and that requires a much more involved and prolonged explanation. To obtain a patent for your software you must apply for a patent in each country that offers patents for software and in which you wish to have the protection a patent can offer. I warned you this was much trickier than how to copyright software. Then it gets trickier still. There is no universal legal definition of what a software patent is so each country that offers patents also has a different definition for what is protected by that patent as well as for why a patent will be granted. If you want to add to the confusion a little more while wondering how to copyright software, also consider the fact that your software may be given a patent in one of the countries where you applied and none of the others. Of course, if this is not enough fun for you, you can try to deal with the red tape involved in dealing with multiple governments in order to resolve any issues or disputes that may have arisen from the result of the software patents you hold. If you've forgotten the original question it was: how to copyright software? I told you that one was much easier. The main thing you need to do if you're going for international patents (which can secure a profitable future for you and your business) is to get a really good patent lawyer and have him walk you through and hold your hand for the entire process. In fact, I would say that's probably the best advice you can get. Patents are complicated and when you're not exactly sure of what you're doing, whom you need to talk to, and what the next step is you stand to waste a lot of time while taking a bigger risk. It is much easier to deal with how to copyright software on your own than it is to work out the complicated world of software patents. If this is your first time designing your own software you have every right to be nervous and excited and scared to death at the same time. Remember lawyers went to school much longer than you in order to know what to do in this situation so you should not be expected to know how to copyright software when you've never done it before.