Welcome to www.taxkingsandqueens.com

Web Hosting - Unix vs Windows-Based Hosting, Which Is Better? An operating system functions largely out of sight, or at least is supposed to. It doesn't matter to non-geeks how a file gets stored, or how memory is used, or how simultaneous processes share the limited resources available on a computer. These are among the basic functions of any operating system. Yet, you can find very passionate supporters - who offer very detailed lists of pros and cons - for every operating system. Why? Because, though the low-level functions of an operating system do their work out of sight, there are many other features that rise to visibility. Sometimes, they do so when they're not supposed to. Weighing the pros and cons objectively could consume a book. But to select a web host operating system, a manageable level of considerations apply. They can be weighed even by those who don't know a processor queue from a pool cue. Learning Curves For most web site owners, administering the site/server is just overhead. It's not something they take pleasure in doing and they have plenty of other things to worry about. Many wouldn't know how and have no interest in learning (rightly so, given their priorities). Consequently, ease of administration is paramount for such people. Whether a Unix-based site (usually Linux these days) is easier to administer than Windows depends on your current skill set and the type of tools and level of access the web hosting company provides. But in general Linux is more difficult to install and maintain than Windows and the learning curve is steeper. FTP and Control Panels Often, you don't have to care. For many, the operating system is fairly transparent. FTP file transfers to get a new web page up to a Windows server are very much like they are to a Linux-based site. The user/administrator simply doesn't see what's behind the curtain. Many companies provide other utilities that completely mask any awareness of the operating system underneath. When that's the case, the web site owner has no reason to care, until or unless they need or want to go 'inside the black box'. Performance Performance issues can be relevant in selecting which operating system host type to choose. But for the most part, that aspect is outside the web site owner's control. Overall performance can be good or bad on either system, depending on many factors that the publisher will rarely see. The issue is a wash, as far as tipping the scales is concerned. What is more likely to be seen by a web site owner, at some point in their (and their site's) development is the database product that can be used to store information. Databases Microsoft SQL Server is relatively simple to use, yet extremely powerful and can deliver great performance. But it doesn't run on Linux. At least, not without special software to emulate Windows, which usually kills performance. On the other hand, with a bit of time invested, MySQL isn't significantly more difficult to learn than MS SQL Server and there are many free installations. Cost may well outweigh other considerations for most on this issue. Programming Languages Last, but not least, there are differences in programming languages that can be (or at least typically are) used on Windows vs Unix. If you have programmers who are skilled in Visual Basic, ASP and other Microsoft technologies, then a Windows-based host will be your preferred choice. For Perl and PHP programmers, Linux is the more common platform of choice. No single factor can push you to one versus the other operating system. And, in the long run, it isn't the primary consideration, unless you just enjoy playing with operating systems.

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.

Web Hosting - Domain Name Changes and How They Affect You New domain names are registered all the time, and ones previously registered expired. Sometimes that's the result of simple neglect. The owner of the name chose not to renew his or her ownership, so the name became available for someone else to use. In rare cases, a highly original mind managed to think of a new one. In the other common scenarios, someone chose to just let it go or sell it. When you choose to change your domain name, there are actually two separate steps involved: releasing the old name, and adopting the new one. But, just as the postal system can have difficulty forwarding your letters when you change your personal name, changing your domain name brings certain difficulties. One of the most prominent is the fact that any name change requires a change to thousands of DNS Servers around the globe. DNS (Domain Name System) is the set of software/hardware components that allows domain names to map to IP addresses. IP addresses are what are actually used 'under the covers' when one computer communicates with another. Note that there isn't always a 1:1 correspondence between a name and an IP address. One IP address can serve multiple domain names and one domain name can have multiple IP addresses. For the sake of simplicity, we'll stick to the common case here. DNS servers around the world maintain internal databases that match the name to an IP address. Not all servers have all pairs of names/addresses. A series of complex routines allows a request to be forwarded when the particular DNS server doesn't have a needed record. When you acquire a domain name that used to be associated with a given IP address, the odds of you acquiring the same IP address are extremely low. In the unlikely case, for example, that you acquired the domain name yahoo.com, you would almost certainly not get the IP address that was matched with it (unless you bought the Yahoo! company). So, as a result of the change, the name/IP address pair is no longer what it was. A similar circumstance exists when you retain your IP address, but want to change the domain name associated with it. In either case, the pairing has changed. The catch is this: when the change takes place, those DNS databases are not all updated instantaneously around the world. Even apart from the limited speed with which computers and networks operate, (and neglecting the human factor if/when the change is made manually to more than one server) the reason is something called caching. In order to communicate efficiently, DNS servers are designed to assume that changes will be relatively rare. Just as with the postal system, you don't move your address or change your name every minute. Since that's true, in general, the name/IP address pair is cached. A cache is a set of stored information that is reused so that fresh information doesn't have to be communicated with every request for a web page or data. A chain of DNS servers pass requests to the last known address. There is usually more than one system between your computer and the server you want to communicate with. Most of the time, that's your current name/address. When you change the name, that pair is no longer valid. In order to propagate the new name/address pair (so the terminology goes), that cache has to be refreshed. Something similar happens when you establish an entirely new name. That name is first associated with an IP address and that pair has to be communicated to DNS servers around the world in order for you to be able to reach any one of them at random. But DNS servers don't do that until they are requested to do so by your action of asking for information from a remote server. Because of that, but chiefly because of caching, it can take quite a while for the new pair to become known around the Internet. Caches can expire and get refreshed in a few minutes or a few hours. It varies. That time can be as short as an hour or less, if the path between your computer and the web server is very simple and only one DNS server needs to be updated. Or, it can take up to 48 hours or more. Though the 'official' range is often given by registrars as 24-48 hours, the average is closer to about six hours. But that's an average. The actual time in any given case can (and does) vary widely. In the meantime, a number of effects can occur. The most obvious is that, since the name/IP address pair can't be resolved properly, you don't reach the server you want. Your browser points to the old one (in the rare case it's still accessible by that name and address), or it simply reports there's no such name at that address. So, when registering a new name or buying an old one, you should establish the site, but not advertise it for at least a couple of days. Better to wait to get visitors than to turn them off by being 'not at home' when they call.