Welcome to makedonikajournal.org
|
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 - Email Issues When you build a web site, you often provide a means for users to communicate with you. One of the most common 'add-ons' to a web site is the addition of some kind of email access. Email is used to sign users up for newsletters, provide communication for administrative issues and a hundred other uses. But, as everyone sadly knows, email problems can occur. Virus infection is among the most common, though the situation is actually better today than in the past. Huge efforts, and some progress, has been made over the past 10 years to reduce the number and severity of virus attacks. Hackers haven't surrendered, far from it. But they're on the defensive like never before. Many of those viruses were (and are) spread through email, usually in the form of email attachments. That's the source of the now-common advice never to open an attachment from someone you don't know. Professionals will often extend that advice to suggest you never open an attachment that's unexpected, even if it's from someone you know. Well-meaning, but computer-challenged friends often accidentally forward virus infected emails. Spam has taken over the top spot for email annoyances. It's estimated by various different professional sources that 92-97% of all email sent today is spam. While the definition varies, spam is generally regarded as any unwanted commercial email sent by someone whom the recipient doesn't know or have a business relationship with. Spam clutters email inboxes, requires people to sift through to find valid messages, and often contains offensive messages in some form. But, it's a fact of life and isn't going away anytime soon. Even though laws are in place, thousands of spammers continue to risk fines or jail for the chance of making money from that small percentage who will open the unwanted email. Other forms of email problems are even more severe for many web site owners. When the mechanisms fail that they rely on to send and receive messages to and from their users, that's a problem. Dealing with those problems can range from sending an email or instant message to an administrator, to tracking down the right person to get your site removed from a blacklist. Email is the communications vehicle of choice for millions everyday. When the system burps, someone has to take time to do something about it. Often, that means relying on a person who is already overburdened with too many issues to resolve. So, besides pointing out some sad facts or complaining, what's the point? All of the above shows just one more area you should look at when selecting a web host or deciding whether to move to another. Just as with server or network administration, companies vary in their ability to deal with email-related issues. Some are responsive and super-competent. Others, are simply indifferent or worse. And many are in between. Email administration, like server maintenance or network management, is a professional specialty. Skill in one does not necessarily mean quality work in another. Finding a web hosting company and/or system that has few email problems, and solves them quickly when they occur, is an important task. Spend some time researching who provides superior support in email. You'll be happy you did. How to Use a Sample Written Proposal (sample written proposal) Writing a proposal is not an easy feat. For many, it is one of the most difficult things they will ever do in their entire lives. However, there is help for those who are confused about the proposal writing process. A sample written proposal can be used as a guide for the confused writer, and can help them with the process of writing their own proposal. Proposals usually have seven components, which include the Table of Contents, Mission Statement, Abstract, Statement of Need, Project Rationale Incorporating Literature Review, Project Narrative, and Attachments. All of these features can be found in sample proposals, which provide writers with an example of how these sections should be organized. A table of contents is used to provide a comprehensive guide to the proposal, so that readers are able to find what they need and find areas of importance within the proposal. A sample written proposal is an excellent guide to writing a mission statement. A mission statement should be 50 words or less, and states the mission of the project. The statement is used to clarify and state the project’s primary goal, and allows the reader to instantly understand what the writer is proposing without reading the entire proposal. The second section of a proposal is the abstract. It is vital to a proposal that an abstract is well-written, and initial proposal reviews or “first cuts” are often based on the abstract. The abstract of a proposal should be written after the mission statement, and should be changed over time, as the proposal develops further. Most proposal drafters will see that abstracts should be clear and understandable to all readers, including lay readers, and should be suitable for publication. Proposal abstracts should be written in third person, and should include objectives, methods to be employed, and the possible impact of the proposed project. Statement of need is the next part of a proposal. Many writers could benefit from a sample proposal when writing this section, because some drafters tend to write about more than one problem, or present their problem incorrectly. The Statement of need is the section where the drafter presents the problem that must be solved. In this section, drafters should avoid circular logic in the development of their statement of need, as it decrees that the lack of a solution is the problem. It is important to use logical progression in the statement of need, and the proposer must prove that they have an understanding of the problem. The statement should be closed with a discussion of what else is being done to solve the problem, and lead into the narrative with a description of how your idea is different and essentially better than all others. The Project Rationale Incorporating Literature Review is the next section of a proposal. All samples written proposals will have this section, as proposals must incorporate a theoretical basis with a discussion of literature. The rationale for the project should come from evidence found in the relevant literature. A sample written proposal will show drafters how to develop this section and show them how all proposals should incorporate current research into their projects. The project narrative is the sixth section of the proposal, which has six main sections. Some organizations require different proposal narratives, so in this aspect, it may be better to obtain sample proposals from several different organizations. The six sections of the project narrative section of a proposal include goals and objectives, proposed activities, facilities, resources, and project management, evaluation, outreach and dissemination, and sustainability. The final section of a proposal is the attachments’ section. Generally, attachments include the bibliography, letters of support/endorsement, and letters of publication. Drafters can also benefit from a sample written proposal when creating this section, as it will provide an example of how the section should be organized and incorporated in the overall proposal. Writing a proposal is an extensive project, and sample proposals can be used to reduce pressure while providing the proper form needed for an excellent proposal. |