Welcome to www.msunderestimated.com

Software company patent A Software Company Patent is the Door to a World of Confusion There is no universal understanding of exactly what a software company patent is. In general, owning a patent allows a company certain rights (or exclusivity) for a prescribed amount of time. Individuals or corporations seeking a patent must apply for a patent in each and every country in which they wish to have one. Unlike copyrights, patents are not automatically granted to applicants and can take quite a while in order to be approved. Another thing to remember, particularly with a software company patent, is that a patent may issue in one or more of the countries in which you've applied but not all of them. The real problem lies in the fact that there really is no central agreement about what a software company patent actually grants among any of the nations so those who are awarded patents may not be getting exactly what they think they are getting in the process. With no universal agreement there really can't be universal enforcement about the laws and the rights surrounding a software company patent. The growth of Internet business and e-commerce in general has led to many patent applications for software, particularly software that was designed for specific business applications. The problem is that while the cases are granted and successfully tried and defended in some countries, other countries offer no enforcement or legal recourse for those who do not honor the software company patent even if the patents were granted in those countries. The fine line between nations about what is and isn't patentable is another challenge when it comes to establishing and honoring patents. In other words, the issue of a software company patent is a rather confusing process at best. Patents differ greatly from copyrights, which are issued automatically and recognized and enforced internationally. Copyrights protect the source code of software from being copied and registration is generally not required in order for your work to be protected. Lately there is a new term, copyleft, which is an obvious play on words and represents the rights to not only redistribute the works that are covered by this but also to modify and freely distribute those modifications. This term is very much in the spirit of many open source types of software and music. The catch for copyleft protection is that the newly created work be distributed in the same manner and spirit in which it was received. In other words if you were freely given the software, then you must freely provide the improvements and modifications you made to that software. Of course this is a long way from the idea of a software company patent. It is also important that you are sure you understand exactly what you are applying for as far as your patent goes. Different countries will grant patents for different things and those are closely regulated and carefully regarded when it comes to software-know what you are applying for and understand what you are being granted. A software company patent means different things to different people in different places and it nearly impossible to get other countries to honor a patent that they would not have granted at the same time they shouldn't expect other countries to honor patents based on their decision to do so either. One unfortunate circumstance surrounding patents is that there seems to be an unequal and obvious disparity between the haves and the have not's. Patent enforcement for software, unlike literature and music is largely subjective. In literature and music, it is rather obvious that the copyright has been abused or that the work has been copied, this isn't as simple with software which is one other reason that software company patent is such a hotly debated subject in the software industry.

Finishing a Masterpiece and Getting it on the Shelves (how to get a book published) Writing a book is a monumental task in itself. The process is long, drawn out and grueling. Even if you thoroughly enjoy writing and writing on the same subject for an extended period of time, you will no doubt be exhausted by the writing of a book. Getting that book published, however, will take even more time and effort than producing the thing in the first place. Are you thinking about writing a book? Have you already written one and now are just wondering how to get a book published? If you are, read on. Here are a few tips on how to get from the starting line to triumphantly crossing the finish line. Writing that Book When starting out writing your book, before you are ready to consider how to get a book published, you may already feel daunted. To write a successful book you need to start out with some original thought. You probably have plenty of originality, but you may have trouble getting your ideas into a coherent flow of information that will be digestible by the general public. The first step is to create a book skeleton. You need to organize your thoughts into a progression of chapters. If your book will be non-fiction, start with a table of contents. Write chapter headings and sub-headings. You will automatically know that you’ll need an introductory chapter, but you should probably leave the content of your introduction for the last step. Organize your chapters so that they build upon one another. The more headings that you can brainstorm to begin with, the easier it will be to fill in your book with a series of short articles that flow into one another. If your writing will be fiction, you will need more of a storyboard. You will need to create cause and effect as well as character sketches. To make your story coherent your characters will need events to react to. Their reactions should become predictable as your readers get into the story. You may need to create some situations for your characters just for the purpose of introducing their traits to the reader. These are very general guidelines about how to begin constructing your book. The actual process will be much more involved as you move closer to finding out how to get a book published. Even after you are finished with the bulk of the content, your goal is still a ways off into the future. Getting to Print The next step in how to get a book published is finding a publisher. There are resources at your local library that will let you know who will be the best candidate for publishing the kind of writing that you do. After a series of queries and correspondence with the potential publishers you may get an invitation to send your manuscript. Then the work begins. A publisher is very experienced in finding books that are marketable. He knows what it will take to get your book to sell. Don’t be offended when his editors tears your writing apart. If they are doing that, you can enjoy the fact that you are on the road to a published book. Expect to enter into a close relationship of compromise and change with the editor as you rework and rework what you have already so painstakingly written. When you are finished you will have a readable and clean and correct manuscript ready for print. The road to getting a book published is a long one, but well worth the effort. Trust yourself, and trust the publisher to create a beautiful masterpiece. Don’t be discouraged if several publishers are not interested in your book. You may have to just keep the first few for yourself, and then again, they may eventually get accepted. Good luck and enjoy the process.

Web Hosting - Changing Web Hosts, Pitfalls and Planning At some point, nearly everyone finds it necessary to change web hosts. It may be just a migration to another server, or it may be changing web hosting companies entirely. Either way, the process is fraught with potential dangers. But there are ways to minimize the odds of problems and maximize your changes of a smooth migration. Plan, plan, plan. Make a very detailed list of everything that is on your current system. Review what is static and what changes frequently. Note any tailoring done to software and files. Be prepared to remake them if the systems aren't transferred properly or can't be restored. Keep careful track of all old and new names, IP addresses and other information needed to make the migration. Backup and Test Backup everything on your system yourself, whenever possible. Web hosting companies typically offer that as a service, but the staff and/or software are often less than par. Often backups appear to go well, but they're rarely tested by restoring to a spare server. When the time comes that they're needed, they sometimes don't work. Do a dry run, if you can. Restore the system to its new location and make any needed changes. If you have the host name and or IP address buried in files, make sure it gets changed. This is often true of databases. SQL Server on Windows, for example, picks up the host name during installation. Moving a single database, or even multiple ones, to a new server is straightforward using in-built utilities or commercial backup/restore software. But moving certain system-related information may require changing the host name stored inside the master database. Similar considerations apply to web servers and other components. Accept Some Downtime Be prepared for some downtime. Very few systems can be picked up, moved to another place, then brought online with zero downtime. Doing so is possible, in fact it's common. But in such scenarios high-powered professionals use state-of-the-art tools to make the transition seamless. Most staff at web hosting companies don't have the skills or the resources to pull it off. Prepare for Name Changes One aspect of moving to a new host can bedevil the most skilled professionals: changing domain names and or domain name/IP address combinations. When you type a URL into your browser, or click on one, that name is used because it's easier for people to remember. www.yahoo.com is a lot easier to remember than 209.131.36.158. Yet the name and or name/IP address combination can (and does) change. Still, specialized servers called DNS (Domain Name System) servers have to keep track of them. And there are a lot of them. There may be only two (rarely) or there may be a dozen or more DNS servers between your visitors' browsers/computers and your web host. Every system along the chain has to keep track of who is who. When a name/IP address changes, that pair has to be communicated to everyone along the chain, and that takes time. In the meantime, it's possible for one visitor to find you at the new place, while another will be pointing to the old one. Some amount of downtime will usually occur while everything gets back in sync. The Little Gotchas But even apart from name and IP address changes, there are a hundred little things that can, and often do, go wrong. That's not a disaster. It's just the normal hurdles that arise when changing something as complicated as a web site and the associated systems that underlie it. Gather Tools and Support Having an FTP program that you're familiar with will help facilitate the change. That will allow you to quickly move files from one place to the next to do your part to get the system ready to go or make repairs. Making the effort to get to know, and become friendly with, support staff at the new site can be a huge benefit. They may be more willing to address your problem before the dozen others they have to deal with at any given moment. Ok. On your mark. Get ready. Go.