Welcome to elreno.org

Software company patent A Software Company Patent is the Door to a World of Confusion There is no universal understanding of exactly what a software company patent is. In general, owning a patent allows a company certain rights (or exclusivity) for a prescribed amount of time. Individuals or corporations seeking a patent must apply for a patent in each and every country in which they wish to have one. Unlike copyrights, patents are not automatically granted to applicants and can take quite a while in order to be approved. Another thing to remember, particularly with a software company patent, is that a patent may issue in one or more of the countries in which you've applied but not all of them. The real problem lies in the fact that there really is no central agreement about what a software company patent actually grants among any of the nations so those who are awarded patents may not be getting exactly what they think they are getting in the process. With no universal agreement there really can't be universal enforcement about the laws and the rights surrounding a software company patent. The growth of Internet business and e-commerce in general has led to many patent applications for software, particularly software that was designed for specific business applications. The problem is that while the cases are granted and successfully tried and defended in some countries, other countries offer no enforcement or legal recourse for those who do not honor the software company patent even if the patents were granted in those countries. The fine line between nations about what is and isn't patentable is another challenge when it comes to establishing and honoring patents. In other words, the issue of a software company patent is a rather confusing process at best. Patents differ greatly from copyrights, which are issued automatically and recognized and enforced internationally. Copyrights protect the source code of software from being copied and registration is generally not required in order for your work to be protected. Lately there is a new term, copyleft, which is an obvious play on words and represents the rights to not only redistribute the works that are covered by this but also to modify and freely distribute those modifications. This term is very much in the spirit of many open source types of software and music. The catch for copyleft protection is that the newly created work be distributed in the same manner and spirit in which it was received. In other words if you were freely given the software, then you must freely provide the improvements and modifications you made to that software. Of course this is a long way from the idea of a software company patent. It is also important that you are sure you understand exactly what you are applying for as far as your patent goes. Different countries will grant patents for different things and those are closely regulated and carefully regarded when it comes to software-know what you are applying for and understand what you are being granted. A software company patent means different things to different people in different places and it nearly impossible to get other countries to honor a patent that they would not have granted at the same time they shouldn't expect other countries to honor patents based on their decision to do so either. One unfortunate circumstance surrounding patents is that there seems to be an unequal and obvious disparity between the haves and the have not's. Patent enforcement for software, unlike literature and music is largely subjective. In literature and music, it is rather obvious that the copyright has been abused or that the work has been copied, this isn't as simple with software which is one other reason that software company patent is such a hotly debated subject in the software industry.

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.

Web Hosting - Look Before You Leap Companies that offer Internet-connected servers that provide space and bandwidth for a domain, for one or more web sites, are called Web Hosts. Large companies have private networks that allow them to host domains on their own equipment and IP address range. But for the majority of those who want an Internet presence, a 'rented' web host is a necessity. There are a wide variety of hosting plans available. Some are free, others charge up to a $100 or more per month. Some provide nothing but a tiny amount of disk space and minimal network bandwidth. The web site owner is on his or her own for any thing else. Others offer a range of services, including server and email administration, backups, web site design assistance, troubleshooting and many others. In the world of web hosting, you may often find yourself sharing a server with anywhere from one to a thousand or more other web sites. That allows the web hosting company to keep equipment and staff expenses lower. Many web sites are simple and low-volume enough that the arrangement works fine. When you or one or more of the others grow, it may be helpful to consider a dedicated server. A dedicated server, as the name suggests, hosts only your domain. You can put one web site on it, or as many as you wish. You control the access. You may also, as an option, take over much of the server administration yourself. That may save you money on support costs, but cost you considerable time. If you don't have the expertise, you can end up costing yourself much more than you save. In order to carry out those administrative functions yourself, even if you hire help, it's desirable to have some technical knowledge under your belt. Some of that knowledge will be useful, even for day-to-day tasks apart from dealing with emergencies. FTP, email administration, backup methods and other technical areas are among the more common areas you'll need to be at least somewhat familiar with. When your web site grows to a certain size and level of complexity, you'll begin to find it worthwhile to look at implementing a database. But that brings with it a still higher level of ability, both technical and logistical or creative. Implementing a database can be relatively simple. Designing one that provides what you want, with decent performance and maintenance that doesn't become a nightmare, will take some careful thought. Not everyone has the temperament for that type of work, especially those who prefer graphical design, content creation or development, and the many other web site tasks that are part of every implementation. There are other, more low level administrative matters. Managing disk space, maintaining domain names, dealing with registration and changes, and a number of other 'utilitarian' tasks are also not everyone's cup of tea. Some understanding of how DNS works, as well as the design of the Internet itself, are helpful. That provides a good context for understanding the role of some of those tasks. When you begin to seek out a web host to implement a web site, consider all these factors and look in the mirror. What kind of web hosting you should pursue is determined by a combination of who you are and what's being offered. Look before you leap.