Welcome to www.bloghaus.net

Some Beginner Tips for Writing a Book (writing a book) Before you begin your book writing adventure, you must research your idea and see if it will fly. Who is going to read it? Who are you trying to appeal to with your words? You must have a general idea of who your intended audience will be. Check out other books. Is there a book already published that resembles your book? What will make your book unique from theirs? If there are similar books already out there, what is going to make your book different and make people want to buy it? If you are still reading, then it is safe to assume that you have your idea under control and are ready to more on in writing a book. Decide on a schedule that is best for you, one that you will be able to stick to. It will be very frustrating to you if have unrealistic expectations and then are unable to stick to them. Your schedule should begin before your research and carry through to the book being ready for publication. Make a detailed outline with the main plot, events leading to that plot, and explicit detail about the characters. By having more information about the character you will be able to become them as you are writing. By having background on them, even if it is irrelevant to the story, it may help while choosing their actions, dialogue, and feelings through out the book. An outline is also a good reference point to come back to double check your timelines and details. You may want to turn of you editing software for your first draft. While writing a book the first draft is when you begin meshing the plot, the characters, and everything together. Grammar, spelling, and punctuation can be fixed later. Remember books do not necessarily have to be written front to back. By writing different chapters or events it may be easier for you to come back and connect them later. Sometimes having the words on the paper and reading will make it easier to fill in the blanks. You are on a role and rough draft is finished. Now is the time to read it. When writing a book reading the rough draft will allow you to make sure that there are no errors in the timeline, that plots link with the characters, and that it all makes sense and flows together. Once you have accomplished that turn your editing software back on. It is time to fix your grammar, spelling, and punctuation mistakes. Now put you book aside. Let it sit for about two weeks or so before you pick it up again. This will give your mind time to be clear and fresh. Now read the book again. Does it still flow and make sense? Do you need to add something or change it? Now is the time. Choose someone to proofread your book for you. If at all possible you should hire a professional editor to do this. But if you cannot ask a colleague or maybe someone else you know with a writing or English background. While giving professional advice they will also be able to offer you and unbiased opinion. They will be able to see if there is a jump in the timeline you didn’t notice or if you had a character in the beginning and they just disappeared. The last thing to do while writing a book is creating the final draft. The final draft should be error free. This is your last chance to change anything before it goes to the publisher. Now is when all that time you spent writing a book comes together to make its trip to publication.

Web Hosting - Redundancy and Failover Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad. Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily. Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams. A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'. A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path. Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy. That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place. And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later. One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem. Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine. The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience.

Copyright music expiration For Many Copyright Music Expiration is a Luxury for Worry If you copyright music, expiration isn't something you have to worry about, at least not in your lifetime. The music that you've written is copyrighted the moment you've put it onto paper or recorded it being played. The reason you don't have to worry about expiration is because the music is protected until 70 years after the death of the author. In the case of your music, that author would be you. This rule about copyright music expiration was first put into place so that the families and heirs of an author could still earn royalties even after his or her death. Ultimately this means that if you've taken the steps to copyright your music and have registered the copyright then your music will be protected throughout your lifetime until 70 years after you or the last surviving author (assuming a collaboration) are no longer living. Copyright music expiration is not something you should make a primary concern unless you are having issues of someone respecting and/or honoring your copyright at the moment. You should take comfort in the fact that as long as you are alive you are the only one who can assign your copyright to another person and as long as you haven't given up your ownership of the music it still belongs to you. This is different however if your copyrighted music was work made for hire. If that is the case then you cannot have ownership of the music, as it never legally belonged to you no matter what form it was in when it changed hands. Works made for hire have different copyright music expiration than those that were owned by the creator. With works made for hire, the copyrights are in effect for 95 years from the original publication date or for 120 years from the creation of the work whichever of the two is shorter. For most beginning musician’s copyright music expiration date isn't as important as getting that first gig or earning that first dollar as a result of the music he or she writes and/or plays. It's about art for many and about survival for others. The latter are quite often the ones that are taken advantage of. These are the authors who don't protect themselves as they should and end up failing to register their music because the idea of buying food seemed more pertinent to survival at the moment. This is often the case, particularly among street musicians and it's something that was becoming a growing problem immediately after hurricane Katrina devastated New Orleans taking with it many of the homes of starving musicians along with many pieces of music that will never become copyright music, expiration or not, those works are gone forever except in the mind of their creators. who could barely scrape together the money to pay $100 a month for a hovel they shared with 6 or 7 other people in order to keep expenses down and avoid living on the streets. The building not only of homes for those musicians displaced as a result of Katrina's devastation is wonderful but even more than that is the fact that there are organizations that are dedicated to creating a community for these musicians so that maybe many of the struggling artists won't be taken advantage of or have to face the decision to register their music in order to protect and copyright music expiration for their future heirs or to risk loosing their claim over the music they wrote in order to eat or pay the rent or buy groceries.