Welcome to elreno.org

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.

ï»¿Copyright music Copyright Music in Order to Protect Future Profits If you are a budding artist seeking to copyright music that you have labored over, there is good news. Many people confuse copyrighting music with registering music and they are two different things. According to the law in the United States, once you have written or recorded your music in a permanent form, it is copyrighted. Of course, it might help to first understand what it means to copyright music in the first place. A copyright is a certain legal protection that is offered to those who compose creative works. Whether those works be art, music, or the written word. According to the U. S. constitution there are limits that can be placed on the amount of time that the work is exclusively protected. If you copyright music, this means that you and you alone have the right to use your work or allow others to use your work. You also have the right to distribute copies of your work. Whether those copies are in the form of written or sheet music or recorded music to the public as well as the right to perform your music for the public. There is something called fair use that despite your copyright; music written or recorded by you may be used for the purpose of research, news reporting, commentary, or criticism. In other words, there are times when the use of copyrighted material is deemed appropriate without the consent of the one holding the copyright. To copyright music alone is not enough in many cases to protect your music, at least not without going through a lot of hoops in order to do so. One of the things you can do in order to protect your copyright is provide notice of copyright. This is a simple step that includes writing a simple statement to the effect of the word "copyright", the date, and your name at the bottom of your sheet music or on the case for the recording or the actual recording itself. CD's are the most common means for recording devices today and a notice of copyright can easily be added to the exterior of your CD or on your label if you have one printed. In case you are wondering: why copyright music? The answer is rather simple, so others cannot take credit for your creative genius. For an added layer of protection you may want to consider registering your copyright as well. Registering your copyright will provide you with formal legal documentation of your ownership of your music should anyone else attempt to lay claim to your music or any other dispute about true ownership/authorship come about. You must have your copyright registered if you wish to file a copyright infringement suit and it is, in my humble opinion, better to not only copyright music early on but also to register your copyright before it could possibly become an issue. Registering while not entirely painless is not as difficult a process as you might think. Basically it involves filling out an application, paying a filing fee (check with the U. S. Copyright Office for the current amount), and a copy of the work being protected (this will not be returned). It's also important to remember that your music doesn't have to be published in order for you to obtain a copyright. Music should be copyrighted and registered long before the publication process in order to protect your rights as the creator of the music. Whether you are dabbling with cute little limericks or writing masterpieces and concertos or are rock and rolls next super star you want to make sure to copyright music earlier rather than later for the best possible outcome should problems arise.

Web Hosting - Sharing A Server – Things To Think About You can often get a substantial discount off web hosting fees by sharing a server with other sites. Or, you may have multiple sites of your own on the same system. But, just as sharing a house can have benefits and drawbacks, so too with a server. The first consideration is availability. Shared servers get re-booted more often than stand alone systems. That can happen for multiple reasons. Another site's software may produce a problem or make a change that requires a re-boot. While that's less common on Unix-based systems than on Windows, it still happens. Be prepared for more scheduled and unplanned outages when you share a server. Load is the next, and more obvious, issue. A single pickup truck can only haul so much weight. If the truck is already half-loaded with someone else's rocks, it will not haul yours as easily. Most websites are fairly static. A reader hits a page, then spends some time skimming it before loading another. During that time, the server has capacity to satisfy other requests without affecting you. All the shared resources - CPU, memory, disks, network and other components - can easily handle multiple users (up to a point). But all servers have inherent capacity limitations. The component that processes software instructions (the CPU) can only do so much. Most large servers will have more than one (some as many as 16), but there are still limits to what they can do. The more requests they receive, the busier they are. At a certain point, your software request (such as accessing a website page) has to wait a bit. Memory on a server functions in a similar way. It's a shared resource on the server and there is only so much of it. As it gets used up, the system lets one process use some, then another, in turn. But sharing that resource causes delays. The more requests there are, the longer the delays. You may experience that as waiting for a page to appear in the browser or a file to download. Bottlenecks can appear in other places outside, but connected to, the server itself. Network components get shared among multiple users along with everything else. And, as with those others, the more requests there are (and the longer they tie them up) the longer the delays you notice. The only way to get an objective look at whether a server and the connected network have enough capacity is to measure and test. All systems are capable of reporting how much of what is being used. Most can compile that information into some form of statistical report. Reviewing that data allows for a rational assessment of how much capacity is being used and how much is still available. It also allows a knowledgeable person to make projections of how much more sharing is possible with what level of impact. Request that information and, if necessary, get help in interpreting it. Then you can make a cost-benefit decision based on fact.