Welcome to elc20.com

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.

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 Form The Copyright Music Form is your First Step to Protecting your Work Many confuse a copyright music form with an actual copyright. The form is actually what you get from the U. S. Copyright Office when you are ready to register your copyright. It is highly recommended that everyone who writes a piece of music take the time and register their copyright. It is also important to understand that once you've either written or recorded your original music, it is actually copyrighted. In other words you do not actually need to fill out any type of copyright music form in order to have your music copyrighted. While registering is not the act of copyrighting your work it is very necessary if you plan to file suit for copyright infringement. It is also better to fill out the copyright music form they offer earlier in the life of your music rather than later as the timing of the registration of your copyright can have an impact on the actual awards you can receive should you win your lawsuit. There is also something quite satisfying about having your musical works registered with the copyright office. I can't explain the feeling as it will be different for everyone but if you've written music, you really should see for yourself. You can find the copyright music form from the U. S. Copyright Office online quite easily. There is more involved than simply filling out the paperwork in order to register your copyright. You must also pay a fee, the actual fee changes so you should make sure you are aware of what the current fee is before sending in your work. An insufficient fee can result in delays. You also must send an actual copy of the music you are registering the copyright on. Your copy may either be the written or recorded music you wish to register but must include everything you wish the registration to cover. When filling out the copyright music form it is important to provide as many accurate details as possible. While your registration is active the day your application is received you may not actually receive your certificate for several months. Really and truly, as far as government agencies go, this is one of the easier ones to deal with as far as red tape. The procedure in addition to the copyright music form is straight forward and not designed in a manner that would be too easily confusing. The copyright music form is only one step in the process of registering your music's copyright. While it is an important step if you forget the other steps there will be delays in the registration process. Read the form completely before filling it out and if you are printing your form from the computer, I highly recommend printing more than one copyright music form to insure that you have extras if you make a mistake and in order to register your future musical copyrights. Your first copyright registration will be the most nerve wracking. This makes perfect sense when you consider that trying anything new requires some degree of 'anticipation'. It is also likely to be your most thrilling. Even in this particular piece of music ends up being the worst piece you've ever written (most of our first endeavors are our worst) there is a lot to be said about the fact that you've actually taken the steps to insure your future is a great feeling. If your first piece of music sells and is someday published that is wonderful. If not, you are still ready for the next piece and have gone through the process of filling out a music copyright form before so you know what to expect.