Welcome to innothai.net

Web Hosting - The Internet and How It Works In one sense, detailing the statement in the title would require at least a book. In another sense, it can't be fully explained at all, since there's no central authority that designs or implements the highly distributed entity called The Internet. But the basics can certainly be outlined, simply and briefly. And it's in the interest of any novice web site owner to have some idea of how their tree fits into that gigantic forest, full of complex paths, that is called the Internet. The analogy to a forest is not far off. Every computer is a single plant, sometimes a little bush sometimes a mighty tree. A percentage, to be sure, are weeds we could do without. In networking terminology, the individual plants are called 'nodes' and each one has a domain name and IP address. Connecting those nodes are paths. The Internet, taken in total, is just the collection of all those plants and the pieces that allow for their interconnections - all the nodes and the paths between them. Servers and clients (desktop computers, laptops, PDAs, cell phones and more) make up the most visible parts of the Internet. They store information and programs that make the data accessible. But behind the scenes there are vitally important components - both hardware and software - that make the entire mesh possible and useful. Though there's no single central authority, database, or computer that creates the World Wide Web, it's nonetheless true that not all computers are equal. There is a hierarchy. That hierarchy starts with a tree with many branches: the domain system. Designators like .com, .net, .org, and so forth are familiar to everyone now. Those basic names are stored inside a relatively small number of specialized systems maintained by a few non-profit organizations. They form something called the TLD, the Top Level Domains. From there, company networks and others form what are called the Second Level Domains, such as Microsoft.com. That's further sub-divided into www.Microsoft.com which is, technically, a sub-domain but is sometimes mis-named 'a host' or a domain. A host is the name for one specific computer. That host name may or may not be, for example, 'www' and usually isn't. The domain is the name without the 'www' in front. Finally, at the bottom of the pyramid, are the individual hosts (usually servers) that provide actual information and the means to share it. Those hosts (along with other hardware and software that enable communication, such as routers) form a network. The set of all those networks taken together is the physical aspect of the Internet. There are less obvious aspects, too, that are essential. When you click on a URL (Uniform Resource Locator, such as http://www.microsoft.com) on a web page, your browser sends a request through the Internet to connect and get data. That request, and the data that is returned from the request, is divided up into packets (chunks of data wrapped in routing and control information). That's one of the reasons you will often see your web page getting painted on the screen one section at a time. When the packets take too long to get where they're supposed to go, that's a 'timeout'. Suppose you request a set of names that are stored in a database. Those names, let's suppose get stored in order. But the packets they get shoved into for delivery can arrive at your computer in any order. They're then reassembled and displayed. All those packets can be directed to the proper place because they're associated with a specified IP address, a numeric identifier that designates a host (a computer that 'hosts' data). But those numbers are hard to remember and work with, so names are layered on top, the so-called domain names we started out discussing. Imagine the postal system (the Internet). Each home (domain name) has an address (IP address). Those who live in them (programs) send and receive letters (packets). The letters contain news (database data, email messages, images) that's of interest to the residents. The Internet is very much the same.

The Job Interview – How to Handle Getting Around a Negatively Asked Question Many dread that day that they have to go for an interview. Looking professionally dressed, acting professional and displaying the knowledge is all important. Employers and interviewers test you for anything and everything that you can think about--from your likes and dislikes to the actual experiences with this type of work to the facts. Most of these questions you can dodge and answer safely and securely. But how about those negatively asked questions, how could you professionally dodge those questions? Often times a reaction to a negative question is what can make or break the deal. Sometimes employers ask these questions on purpose to see what your reaction might be and to be able to determine first of all your character and second of all, if the negative event in your life is related to a good or bad character. So how can you master these questions and possibly pass the tests? One of the most important factors when getting prepared to dodge difficult questions is to be secure and knowledgeable about any points on your résumé and in your life. If you have a good answer prepared for difficult situations that happened in your life, it will be an ease for you to get around negatively asked questions. Whenever an interviewer asks you a negative question, make sure you stay calm and do not answer hastily. Sometimes it is enough to give a very short answer and it does not necessarily need a complete explanation that might get you stuck. The longer the answer you try to make up, the easier you might stumble over something and then fall hard. When trying to get around a negatively asked question, besides that fact that you need to stay calm and give a short answer, try to get to a different topic. Strike up a conversation about your more positive skills and accomplishments and therefore get around that question that might have bothered you otherwise. In some instances, depending on the content of the question, it might even be best to answer truthfully. What if you were asked about staying home for no obvious reason? At least according to your résumé there is no job, no new degree or similar mentioned. Maybe it was for a sick relative or the birth of a baby? Why not use the truth in these cases as an answer. When answering difficult questions you might have to decide often on the spot how to answer. In any case, it will almost never help you to make up a lie for a negatively asked question. A lie can get you into a situation you cannot get out of, but the truth can never get you in a worth situation than you are in by answering the questions truthfully. If you do not want to answer truthfully because you think it can hurt your image, sometimes it then is better not to answer the questions. Try to divert the attention successfully to another more positive topic such as your achievements, earlier project or similar other experiences that led to a positive result. Keep in mind that the interviewer is testing to see if you are a good fit for the company and they do not exactly know you. They know a few facts about you, but the do not know the whole picture and especially not about the more negative things they might want to find moiré information about. So when going for a an interview and trying to get around a negatively question, make sure to be honest or to not get into details if you do not want to discuss the issue, but mainly make sure that you stay calm, do not get excited about it. A calm confident person can easily answer any and all questions that might be posed to him or her.

Web Hosting - Do It Yourself Administration, Things to Consider The choice of whether or not to try to administer your own web site brings with it a host, pun intended, of issues. For most web site owners, the primary focus is naturally on creating, maintaining and enhancing the site. That often is just part of managing an entire business, for which the web site is just the means to an end. That implies there will be little interest in or time left over for technical administration like database maintenance (tuning, space management, security, bug fixes), establishing and maintaining backups to ensure they're successful and usable, email administration, disk space management, applying operating system fixes for bugs and security, and other tasks. But cost is always a factor in any business. Paying for technical help can burden the budget of a new and struggling business. Consulting fees can range from a few dollars an hour to over $100. On the lower end, the poor skill level and quality of work will make it not worth even that small amount. On the higher end, you can quickly rack up expenses that will bust your business. Permanent employees are usually somewhere in the middle of that range when you add up salary, employment taxes and more. Often, server and/or web site administration can be paid for as part of the web hosting package. That cost is usually lower than independent contracting help, but those staff are usually tasked with maintaining dozens if not hundreds of servers and sites. They can, therefore, give very little individual attention to yours. Often, novice web site owners are intimidated by some of the technical requirements for server or site administration. But, as with anything, a little familiarity can show that the knowledge required is more modest than one might expect. Administration in many cases involves fairly elementary, and frequently repetitive, tasks. These can be learned easily. Using a test site or a free hosting service is a good way to practice and learn without risk or cost, other than time invested. Once that initial hurdle is jumped over, administration can be done quickly and some even find it interesting. It allows the site owner to exercise additional control over the total product, and there's satisfaction in being able to say 'I did that' even if you prefer not to do it forever. That real-life learning experience also allows the site owner to better judge any consultants or staff that are hired. It's much easier to judge if someone is providing you with an accurate assessment of a problem if you've solved it yourself. Any time-estimate they provide to fix it can also be better calculated if you've had to do it yourself. Every web site relies on a variety of factors, usually unseen, in order to continue to function properly. But the fact is that they misbehave from time to time. Deciding whether to tackle those problems yourself depends on your available time and skill set, and what it will require to get things back on track. In other words, it's a standard cost-benefit analysis that everyone has to undertake every day in life.