Welcome to elreno.org

Web Hosting - All About Domain Names "What's in a name?" Shakespeare asks in Romeo and Juliet. In the case of your web site the answer is: quite a lot. A domain name is the English (or other) language designator for your site. Because of the way the Internet functions, that name is associated with an IP address, a numeric identifier that computers and network components use to connect a browser to a web site. It's not mandatory that a site has a name. But directing visitors by IP address can quickly generate difficulties. Having an IP address IS mandatory, since it's ultimately the way a web site is located by other computers and network software. In the early days of the Internet the name was chosen carefully in order to help a person remember the URL. That made it easier to type, too. With hotspots on a page, great search engines, social networking and other contemporary tools, that's not as important now. But from a marketing perspective, it still helps to have a good name. It's still beneficial to have a site called 'CheapTVs.com' if what you sell are inexpensive TV sets. Calling your site, 'InexpensiveElectronicVisualDisplayDevices.com' may describe your business in some way, but it's a little harder to refer a new person to your site. Which name you choose can, therefore, affect how much traffic your site gets, how soon. Sooner or later, if you have information and/or products/services that people want, word will get around. But having a good name can certainly help. Love them or hate them, the Google company chose well. Of course, the fact is that there are millions of web sites around the world. That means, you don't necessarily get the name of your first choice. ICANN (Internet Corporation for Assigned Names and Numbers) is the internationally recognized authority for managing IP addresses across the worldwide Internet, along with the top-level domain name-parts (.com, .net, .org, .edu, and so forth). But registering a name is done by simply contacting any of a hundred organizations that work as intermediaries to establish and track the names. GoDaddy, Register.com, Network Solutions and a great many others provide the service for anywhere from free to a few dollars per month or year. You contact them by navigating to their web site. Then, using a feature they all provide, you can select a possible name. They use something called whois and other software to determine if the name is already claimed. Or, you can check yourself at www.whois.com. Registration is for a limited time, but typically renewable in perpetuity provided you pay the (usually annual) fee. You may have to go through several choices to find a domain name that isn't already in use. With so many millions of sites, the odds of you getting your first choice is slim, unless you have a highly unusual imagination. But, it's also true that domains tend to die or expire. As they do, the name becomes available for use by someone new. A method for getting on a 'waiting list' is available. You register the name you want and if and when the name becomes available, you are offered the chance to claim it. Naturally, there's competition even on the waiting list for 'good' names. There are many different ways of establishing priority that vary by company. At any given time there are thousands of so-called auctions going on to bid on names. Give some thought to your new domain name and research its availability, but don't stress over it. The name isn't everything. After all, if Google had built a search engine that delivered usable results only 10% of the time, their name would be mud.

Web Hosting - FTP and Other File Transfer Tools Anything related to the Internet or computers is bound to introduce technical issues pretty soon. One of the earliest that novice web site owners encounter is FTP, which is an acronym for File Transfer Protocol. Seeing it spelled out, it's easy to see why those in the know quickly move to speaking in short hand. The reason web site owners soon will (or need to) become familiar with FTP is obvious to anyone who has built a site on a remote server. You have to have some way of getting the files to the remote computer and FTP is one of the most common tools. It's also one of the simplest and most efficient. FTP is composed of two parts: the client software and the server software. It's similar, in a way, to talking to someone on the phone who writes down everything you say. You (the client) make a request ('transfer this file to the server') and the listener (the server) takes the request and acts on it. That request to copy a file from a local computer to the remote one is carried out (often 'under the covers') by a PUT command, as in PUT this there. You create the web page (in the form of a file) and then PUT the file on the server. To move a file in the opposite direction, from the remote server to your local computer, your client software issues a GET command. Many FTP clients have graphical interfaces, similar to Windows Explorer, that allow you to drag-and-drop or otherwise copy the file without ever seeing the actual commands that carry it out. But it's helpful sometimes to know what goes on underneath. In tricky cases it can be an advantage to use a command line interface (in Windows, the 'DOS box', with a similar interface familiar to most Linux users). Knowing the commands and being able to use them in the command line form can sometimes help you diagnose what is going on when the graphical tools misbehave. But FTP is not the only way to get a file from here to there. In fact, your browser moves files around from a remote computer to your local one all the time. In most cases, when you type in or click on a URL, what happens under the covers is in essence a file transfer process. The web page is transferred from the web server to your local computer then displayed by the browser. Alternatively, you can sometimes even email a web page/file from your local computer to the remote server, then use an email client on the server itself to get the file and put it in a folder. That requires that you have some form of access to the remote computer. But there are many ways of doing that, such as in-built utilities in the operating system or using commercial remote control programs. Those alternatives can be helpful to know in cases where the FTP file transfer process is misbehaving. Having more than one way to accomplish the task helps you diagnose what might be going wrong. It also helps you get the job done when the usual tools aren't cooperating. The more you learn about these sometimes puzzling acronyms, the easier you can accomplish your own goals.

Web Hosting - Databases, What Are They and Do You Need One? 'Database' is one of the most commonly used terms that one encounters in web site design. Yet, what they really are and whether they're essential is often not clear to novices. A database is a collection of organized data, stored in files that have a specific structure. It's that organization and structure that allows for easy and rapid storage and retrieval. The need for a database generally only arises when you have a certain amount of information and that information needs to have some structure. If you have a half-dozen names and addresses to store, a database is usually overkill. If you have a blob of data with no relationships between any of the items in that blob, maintaining a database is usually more trouble than it's worth. Maintain a database? Yes, like other complex systems a database, to be effective, needs to be designed properly at the outset then kept 'tuned' for good performance. The alternative is to gradually allow the database to become more and more disorganized. That leads to difficulty in use, poor speed of retrieval and more frequent failures. With MySQL, Access or MS SQL Server, the three most common choices of database product for web sites today, setting up a database is relatively simple. Even those with limited technical skill can get one up and running just by following some simple instructions. But some thought should be given to how you want the information organized, and to maintaining the system during its lifetime. Suppose you have a set of names, addresses, email addresses, products purchased, date purchased and amount. If you have only a few dozen records it matters very little how these pieces are arranged and related. A database usually isn't even warranted in this scenario. Once you have several thousand or more records, it matters a lot. Speed, the ease of expanding the set of attributes (like adding, say, product category), and other issues come into play. Even those with little technical expertise, but a willingness to exert logical thought and invest some time, can build a very robust database. Think about how you would organize a set of data (called 'tables'). Should Name, Address, and Product be in the same table? Or should the personal information be stored in one table and any product information (product, price, ...) in another? Some experimentation may be needed to get it right, but the choices have an impact on how easy the tables are to maintain. It also affects the speed with which programs can fetch old data and store the new. Having a database also introduces new maintenance issues for the server administrator, since backups usually need to be done differently. Recovering a failed database is usually more complicated than simply re-copying files from yesterday. Ask your hosting company what tools and skills they have for dealing with any database system you consider. It's true that introducing a database creates more complexity and the need for additional thought and administrative effort. At a certain level, professional expertise will be needed. But clearly the advantages outweigh the costs in many cases. Companies large and small eventually use databases to store and organize data. At some point, you may be fortunate enough to be one of them.