Welcome to taxkingsandqueens.com

Patent and copyright law Understanding Patent and Copyright Law Patent and copyright law gives the inventor the exclusive rights to the invention. No one else can produce the invention for a set period of time under patent and copyright law. Patent and copyright law is set up to protect inventors. The law on patents can be found in the United States Constitution, Article 1, Section 8 and in Title 35 of the United States Code. The agency that is in charge of patent laws is a Federal Agency known as the Patent and Trademark Office. Anyone who applies for a patent will have their application reviewed by an examiner. The examiner will decide if a patent should be granted to the inventor. Individuals who have their patent application turned down can appeal it to the Patents Office Board of Appeals. Just because someone has a patent does not mean that they have the right to use, make or sell the invention. For instance, if a drug company comes up with a new drug, they can get a patent on it. However, it would not be available to be sold to the general public until the drug becomes approved by other regulatory bodies. Likewise, someone may invent an improvement to an existing product, yet they will not be allowed to produce or sell the item until they obtain a license to do so from the owner of the original patent holder. For someone to receive a patent, as stated, they must fill out an application on their invention. The application will entail the details of the invention and how it is made. In addition, the person applying for a patent must make claims that point to what the applicant deems or regards as his or her invention. A patent may have many claims with it. The claims protect the patent owner and notify the public exactly what the individual has patented or owns. If someone infringes upon patent and copyright law, it is usually enforced in a civil court setting. The owner of the patent will generally bring a civil lawsuit against the person who has infringed upon their patent and ask for monetary compensation. In addition, the patent owner can seek an injunction which would prohibit the violator from continuing to engage in any acts that would infringe upon their patent in the future. Many patent owners will make licensing agreements (or contracts) with others. These agreements allow another person or company to use someone’s patented invention in return for royalties. In addition, some patent holders who are competitors may agree to license their patents to each other to expand both of their profits. Most everything we use in our day to day life was invented by someone. That person had to seek out a patent for their invention. Patent and copyright law protects inventors from having their ideas and inventions stolen out from under them. This makes the playing field more level for individuals. Without these laws, the marketplace would be out of control and the small guy would probably be eaten alive by big business

Important Networking Follow-Ups: How to Get Those Job Leads Calling When you leave a networking event, you may be buzzing at the prospects offered by all of those new contacts you made, but soon, the cold reality sets in. How will you be able to convert those contacts you made over a glass of wine into valuable business opportunities for you? Successful networking is all in the follow-up. If you’re looking for a job, following up is all the more crucial. Without touching base after a networking event, you become just another face in the crowd of job hunting hopefuls. The first important rule for following-up with networking contacts is to lay the foundations for the follow-up during the initial meeting. At networking events, there can be a lot of empty promises thrown around. Use that first meeting to convey the message that you haven’t gotten caught up in “networking fever” but instead that you are very serious about exploring the job opportunity that you’re discussing with your new contact. Ask the contact when would be a good time to follow-up with them, and then reiterate the information back to them at the end of your conversation: “I look forward to speaking with you Friday at 2 p.m.” If they don’t give you a specific time, then suggest one to them. This rule holds true even if your contact is giving you a lead on a job not with them but with another contact of their own. Let them know you appreciate the information by saying, “Thanks. I will plan on calling Mary on Monday afternoon at 1 p.m.” Not only will this convey your seriousness about the opportunity presented to you, but it may also get you some handy inside information, as the contact may reply, “Oh, no, Mary will be out of town until Thursday – call her then.” The next important rule to networking follow-ups is to follow up with EVERY lead a contact gives you. If a contact suggests that you call someone whom you know won’t really be able to help you in your job search, call him or her anyway. Otherwise, when your contact finds out you aren’t taking their advice, they may just decide not to give you any more the future and any business person can tell you that you never know from whom the most valuable lead will come some day. Keep the lines of communication open by giving any and all suggestions a whirl. Last but not least, do the actual following-up. Follow up with your contact exactly when you said you would, and in the exact manner you said you would (phone, email, letter, etc). If for some reason you can’t make contact at the arranged time, keep trying. If you haven’t made arrangements for a follow-up with a contact, then the rule of thumb is to follow-up with them as soon as possible after meeting them. Try to at least send an email or letter the next day saying what a pleasure it was to meet and that you look forward to talking more in the future, and then say in that note when you plan to follow-up with your contact by phone. Then, of course, stick to that new follow-up obligation. Even if the promises made by a contact while networking don’t pan out for you on the job front, don’t cross them off of your contact list. Keep them in the loop about your job search and your career goals. While they may not have been able to make if happen for you this time, you never know what they might be able to do for you in the future. Your most promising business contact may be someone you already know.

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.