Welcome to ucgstp.org

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.

International Software Copyright International Software Agreement is a Matter of National Security Is there one governing law concerning international software copyright? According to agreements by the World Trade Organization (WTO) and the Trade-Related Aspects of Intellectual Property Rights (TRIP) any software written has an automatic copyright. This is a pretty conclusive consensus as far as an international copyright goes. The short answer would have been yes, but this was so much more informative. An international software copyright should not however be confused with a patent. Copyrights provide creators with the ability to prevent others from directly copying the code involved. A patent can actually limit the use of the software. Because of this, I'm sure you'll understand that patents are a hotly debated topic when it comes to software. The biggest thing to know about international software copyright is that your code is essentially protected the moment you create it. This is, unless you have some kind of contract through your employer that all code created by your belongs to them (these cases have been known to happen and provide excellent incentives for employees to always read the fine print). The problem that many companies are running into when it comes to enforcing international software copyright is that computers are not permanent fixtures in a company. Computers are rather disposable hardware when it comes to keeping up with evolving technologies and software needs to be updated when new computers are purchased. Rather than purchasing new copies of software when the computers are replaced companies are notorious for reusing old copies of the software. They are also famous for replacing 10 computers with the software installed with 40 new computers and installing the 10 copies of the software on all 40 computers. This is not in keeping with international software copyright. This is stealing and you'd be surprised at some of the good upstanding companies that do this on a regular basis. There really are no major differences between traditional policies for American copyright and international software copyright which makes legal issues, troubles, and woes that much easier to deal with. By having a unified international front thee are ramifications and legal actions that can be taken around the world without going through a great deal of international red tape. If you think dealing with the American government is bad, you should see how much fun it is to deal with the American government and another government for a legal action. The agreement between nations for international software copyright is probably one of the soundest possible decisions that can be made as military secrets of all governments have some degree of software in order to keep them operating. While it isn't quite as simplistic as stealing a computer program to unlock the defense secrets of a nation, having access to certain source codes could be problematic in the absolute best-case scenario. Keeping secrets isn't the only thing that makes this agreement so valuable, it is however, one of the most vital. Perhaps one of the greatest things to come about as the result of the international agreement to protect and honor software copyright is the peace of mind that is available to software developers in America and other technologically advanced countries that their source code won't be allowed to be stolen and used against them at a later date by someone in a developing nation with cheap labor and other overhead costs that American corporations simply cannot compete with. This could be devastating to the economies of technological societies if it were allowed to happen and the agreement for an international software copyright prevents that from being allowed to occur.

Conducting a Self-Evaluation After Getting Fired Sometimes life is hard and when you get fired, it gets even harder. In a country where employee turnover is high and there are no laws to protect you at your work place, potentially anybody is at risk to be fired. In general, that is true, but companies usually only fire a person that has done his or her job improperly, or is not qualified for his or her job any more. Therefore after you get fired, it is time that you conduct a self-evaluation. First of all, you need to make sure you know the reason why you have been fired. Do not just assume, you know why you have been fired. Make sure that your employer tells you the exact reasons why he has fired you. A self-evaluation as to whether the employer is right and whether you might have to work on yourself can only be done after you know why the company has told you to leave. If it was tardiness and absence of work that has gotten you fired, you need to be self critical enough to see that you need to be on time and be at work every day that you are not taking a vacation day. Keeping a job means playing by the rules and these rules do include times that you have to be a t work if you want to keep the job. When your boss told you, that you are not accomplishing your work or you are not qualified for the position, think back and try to find out why he might have said that. Did you deliver your work on time? Was it correct, mostly without any problems and errors? If that is not the case, then perhaps your boss was right and maybe you were not qualified enough to do the job. It might be that you need some more training or some more classes at the university to be able to do your job right. Or maybe you have just chosen a job that is not for you. When you are conducting that self-evaluation, make sure you are not too hypercritical. If it clearly was your fault that you got fired, you need to improve yourself and the personality traits that have led to the firing. Sometimes even though your boss gave you an explanation why you have been fired, you might not agree with the reason you have gotten fired from your company. Yes, sometimes these reasons might not be right. Since this is a society where anybody can get fired, maybe you have been fired because your boss did not like you and he made up some dubious reason for firing you. This is why you have to conduct a self-evaluation to make sure if what you were told is the truth. A self-evaluation might also lead you to the conclusion that you need to choose a different profession than the one you have been in. Maybe it took to get you fired to ser you in the right direction and at some point in your future you might actually thank that boss of yours that he had fired you. Otherwise you might have never found the job that you were destined for and would have been miserable doing the job you were doing. Unhappy employees are not good for a company and some bosses are good enough to realize that. Whatever the reason is that you got fired, make sure you find the reason and check with yourself how much truth lies within that reason and do you have to change to be a better employee and be able to keep your next job.