by: Stone Julian
It has become difficult to keep up with the meanings of all the new phrases and terms generated by modern technology. One of the most commonly used phrases on the world wide web (www) today is "Web 2.0." It seems like every web solutions company is using this phrase to sell its stuff. So to the average Joe who's not a geek, what is "Web 2.0"?
Well according to Wikipedia, the free online encyclopedia…
"[T]he phrase Web 2.0 can refer to a perceived second generation of web-based communities and hosted services — such as social-networking sites, wikis, and folksonomies [collaborative tagging schemes] — which aim to facilitate creativity, collaboration, and sharing between users. The term gained currency following the first O'Reilly Media Web 2.0 conference in 2004. Although the term suggests a new version of the World Wide Web, it does not refer to an update to any technical specifications, but to changes in the ways software developers and end-users use webs. According to Tim O'Reilly, 'Web 2.0 is the business revolution in the computer industry caused by the move to the Internet as platform, and an attempt to understand the rules for success on that new platform.' Some technology experts, notably Tim Berners-Lee, have questioned whether one can use the term in a meaningful way, since many of the technology components of 'Web 2.0' have existed since the early days of the W!
eb."
There is no doubt the www has advanced significantly since inception, but there really is no new version of the www. It is simply much more useful to the everyday person.
However, if we counted each major innovation as a whole number and each minor revision as a tenth, we would already be into double digits. So why are we calling it "Web 2.0"?
If you have seen the latest Die Hard movie, or ever bought software for your computer, you will understand why we are not in Web 2.0. Even if we call it Die Hard 4.0 or MS Office 2007, it's still basically the same movie or tool. So what we are really experiencing now is more like Web 16.0.
If you have an in-depth, honest conversation with your web designers, they will tell you that Web 2.0 is a myth. So to explain how we got to Web 16.0, here's a history of the most significant events on the www.
WEB 0.1 -- 1958 – SAGE – Radar systems are first networked
WEB 0.2 -- 1960 – Packet switching is first created
WEB 1.0 – EMAIL – "A New Way to Send Unsolicited Mail Is Born"
Although the exact history of Email is a tad murky, it is generally accepted that it appeared in 1965, and was created so that people accessing a mainframe could communicate with each other. This was the first step in the interconnection of people, facilitating almost instant communication at no cost to the user.
WEB 1.1 -- 1967 – Markup language is created
WEB 1.2 -- 1969 – ARPA – A link is established between computers
WEB 1.3 -- 1696 – ARPA Net – First packet-switched network created
WEB 2.0 – WYSIWYG – "What You See Is What You Get (sometimes)"
With the invention of WYSIWYG in 1970, users could now be presented with a basic display of what their finished product would look like, as they were working on it. This removed the need to memorize complex code.
WEB 2.1 -- 1970 – ASP – First Application Service Provider (SAAS)
WEB 2.2 -- 1970 – Style sheets are created
WEB 2.3 -- 1971 – @ is created to separate hosts and users
WEB 2.4 -- 1973 – TCP/IP is created to simplify networking
WEB 2.5 -- 1973 – First connection to another country established
WEB 2.6 -- 1974 – The term "Internet" is adopted
WEB 2.7 -- 1976 – X.25 – The first network standard is approved
WEB 2.8 -- 1978 – International packet switching service created
WEB 3.0 – USENET– "The Black Market of the Internet"
Usenet was established in 1980 to offer mail and file transfers as well as give personal users access to news. Usenet is in fact a large network of servers all in communication with each other; a user posts something to the local server and that item is passed along to the other servers. Usenet was a major turning point because users could finally have an open conversation with anyone on the net, without needing to specifically know the user (unlike Email). The downside is that with a sometimes un-policed net capable of file transfers, the Usenet of today is a haven for piracy of all types, where anything you can imagine is accessible.
WEB 3.1 -- 1979 – Email is made available to personal computer users, millions of Nigerian Princes suddenly need public help
WEB 4.0 – REAL TIME CHAT – Going Outside Deemed "Obsolete"
Real-Time Chat was created in 1980 following users' frustrations with Usenet articles sometimes taking 24 hours to be updated. This signaled a turning point: online conversations became instant, albeit isolated into segregated groups.
WEB 4.1 -- 1980 – First ISPs created providing dialup internet
WEB 4.2 -- 1981 – TCP/IP becomes a standard
WEB 4.3 -- 1981 – US/Europe/Canada/Hong-Kong/Australia connect
WEB 4.4 -- 1983 – TCP/IP becomes the only standard
WEB 4.5 -- 1983 – First wide area network using TCP/IP operational
WEB 4.6 -- 1985 – FTP – The File Transfer Protocol is created
WEB 4.7 -- 1988 – IRC – Internet Relay Chat is created
WEB 4.8 -- 1988 – Bulletin Board Systems and Forums created
WEB 5.0 – HTML/HTTP/Web Pages – "It Has Begun…"
Around 1980, many researchers were using the internet, but they had no single way to create/display "documents" (web pages). Physicist Tim Berners-Lee and his colleagues needed a simple system for creating/displaying documents, but found that existing systems were too commercial, platform-specific or complicated for the average user. So they created their own relatively simple system, consisting of browsing software called "WorldWideWeb," a protocol for transmitting the information (HTTP) and a document annotation convention called "Hyper Text Markup Language" (HTML). This meant anyone could now create web pages using their simple language.
WEB 5.1 -- 1989 – Images can now be animated, oh the horror!
WEB 5.2 -- 1990 – The network now covers the entire world (publicly)
WEB 6.0 – Search – "Did You Mean: Google?"
Before 1990, there was no way to find a page; you had to know the specific location. Around 1991, search engines began indexing (storing) the content they found, giving users the ability to search for a page even if they didn't know the page's location.
WEB 6.1 -- 1991 – DNS – Dynamic Naming System is created
WEB 6.2 -- 1991 – The first text-based browser is created
WEB 7.0 – DHTML – "Because Non-Scrolling Text Is Boring"
The web was static until Dynamic HTML (DHTML) was created. DHTML introduced client-side scripting, allowing authors to include code in their web pages that performed an action upon being downloaded onto a user's computer. DHTML introduced rollover buttons and drop-down menus on web pages. It goes a long way to making the web more personalized.
WEB 7.1 -- 1993 – The first graphics based browsers are created
WEB 7.2 -- 1993 – Screen casts are first created
WEB 7.3 -- 1994 – Wikis are created; Britannica begins holding its breath
WEB 7.4 -- 1994 – The World Wide Web Consortium is formed
WEB 7.5 -- 1994 – CSS – Cascading Style Sheets created
WEB 8.0 – ONLINE DIARIES – "Teens Reportedly Misunderstood"
Online diaries were first created in 1994 as a means for people to store their diaries online for personal or public reading. Writers could now reach almost anyone worldwide at practically no cost, and everyone could create editorials on whatever subjects they liked, without fear of censorship.
WEB 8.1 -- 1996 – The first social bookmarking site created
WEB 9.0 – RANKED RESULTS – "The Online Popularity Contest"
Search engine results helped find things, but many of the results were useless or had nothing to do with the keywords used. As of 1996, search results started to be ranked based on a multitude of things, like how popular a page is. This made searching faster and easier, and significantly less painful.
WEB 9.1 -- 1996 – Flash is created, whole websites can now be animated
WEB 9.2 -- 1997 – The term "Blog" is adopted
WEB 10.0 – HIRED BLOGGERS – "Wow Isn't Product X Great!"
As of 1997, personal diaries began to evolve to what became known as "blogs." Many corporate websites and personal homepages had (and still do have) news sections, these were traditionally updated manually in a back-end system. With the advent of blogs, the commercial sector jumped in, seeing a new marketing medium.
WEB 10.1 -- 1998 – The first audio news site is created
WEB 10.2 -- 1999 – The first web-based operating system is created
WEB 11.0 – RSS – "Newspapers Deemed Obsolete"
Really Simple Syndication (RSS) was created due to the lack of a universal feed format. The creation of RSS means that users could now "subscribe" to feeds containing video, audio, text, or graphics. Users no longer had to trawl the web for new information, they could "subscribe" to a feed and have it sent to them directly.
WEB 12.0 – REMOTE SCRIPTING – "Waiting For 4 Seconds Now History!"
Remote scripting allows scripts running inside a browser to exchange information with a server, so that scripts could be triggered locally, processed remotely and have information returned directly to the browser. This made the web faster and easier to use, and removed the need to refresh the page for simple tasks like sorting.
WEB 12.1 -- 2001 – Blogs evolve from online diaries
WEB 13.0 – PODCASTING – "Now Everyone Can Avoid Listening To You By Choice Rather Than Circumstance!"
Podcasting originated as a portmanteau of the iPod® and broadcasting, although "portable on demand broadcasting" has now become the widely-accepted definition. Originally Podcasting was created to allow individuals to distribute their own radio shows, but it has become popular for a wide variety of things, from educational materials to the latest gaming news. Podcasting opens up distribution of audio content to anyone with a server, with users "subscribing" to the RSS feeds that appeal to them.
WEB 13.1 -- 2002 – Folksonomy is created, giving rise to "tags"
WEB 14.0 – VIDEO PODCASTING – "Web-Based One-Sided Conversations"
Shortly after Podcasting became popular, video Podcasting was created as a means to send the equivalent of TV episodes to users. Though similar to podcasting, the content was not limited to just "TV episodes". Video Podcasting opens up the video medium so that making a TV show is possible for anyone.
WEB 15.0 – VOIP – "High Tech, Dodgy Sounding Free Calls"
With the Voice Over Internet Protocol, telephone audio is sent over the internet, rather than a traditional phone line. This removes almost all cost involved, and also removes the need to have a physical phone line. What this means for consumers is calling becomes much simpler, easier and significantly cheaper.
WEB 16.0 – SAAS – "The Industry Makes a SaaS of Itself."
Software as a Service (SaaS) is just a new term for a concept that has been around since the dawn of the internet (ASP from 1970). SaaS refers to using a piece of software run/provided through the internet, and instead of paying a large one-off purchase price, you "rent" the software for as long as needed. So while SaaS is the buzzword of the day, the concept is decades old.
..The CONCLUSION?
So if you follow the basic rule that each total upgrade is a new ".0" then we are nowhere near Web 2.0. The story is really one of falling price, increasing reliability and bandwidth, coupled with ubiquitous access.
Simply put, "Web 2.0" is just shorthand for the development process outlined above. Bottom line, the web really becoming what the web really always should have been.
Custom Search
Sabtu, 28 Februari 2009
Kamis, 26 Februari 2009
The 7 Most Common Mistakes Using Packet-Sniffers
by: Barry Koplowitz
This article is also covered in a "The Sniffer Guy" podcast--available at http://www.interpathtech.com --and--through iTunes.
1) Believing the “Intelligence” of the Software without understanding how it makes determinations.
Software default settings are very seldom correct for YOU. For example, a device may say that a SQL server should respond in 50ms. But, if that device is across a WAN with a 200ms ping time--that is highly unlikely. This causes false SLOW SQL messages. This is only an example, but there are many such alerts and messages based on default "thresholds" within this type of software tool's configuration.
Particulars of your environment may create false alerts or other messages. The definitions of what is an “excessive” delay--latency--broadcasts, etc, are up to you--not the tool.
It's important for you to know the default settings driving alerts and messages. Then, ignore or alter those alerts that are not set best--for your enterprise. Altering them to make the appropriate settings for your enterprise is the best strategy. Too many false flags or alerts numb you into ignoring important ones or--cause you to make serious errors and incorrect decisions that can be Very Very expensive.
Properly used, those features can save enormous amounts of time and show things your own eye would likely miss.
2) Not understanding the Protocols used, such as TCP, HTTP, etc.
What good is a tool that tells you information about how a protocol is behaving if you do not understand the underlying technology? By this I mean the RFC's for the protocols that are relevent to your concerns.
---What is the impact of various protocols working differently for the same application doing the same transaction--in different locations?
---What is expected according to specs--and how is your trace file showing different--or less optimal behavior?
---Why would there be 2 TCP connections from one location and 10 from another--for the same application doing the same transaction?
This short article cannot answer all these questions--but it can show you the types of information that you will need to understand in order to make sense out of the data a trace file will show you. Know the protocols well. Deep understanding of TCP is the basic price of admission. While you may consider this a matter of skill sets, my point is that attempting to troubleshooting a problem with a packet-sniffer while not understanding the protocols is a mistake--and a common one. If you add this point to the first one listed--about not believing all the standard settings on tools--you find that the tool cannot answer anything for you by itself. You need to know what you are looking at. You are the analyst--the tool is just an aid.
3) Not understanding the layer 1 and layer 2 aspects of the topology you are sniffing.
Ethernet and all other topologies have many different specifications, which are altered or outright ignored by many switch or other network device manufactures. You must know the specs and how the hardware you are working with applies those specs--or doesn’t apply them. A classic example is Spanning Tree. There are IEEE specifications for Spanning-Tree but those specifications are just a model...not a law. Each manufacturer has tweaked it in order to create some proprietary advancement to give them a competitive advantage. Sometimes, those advances become the new spec. However, you need to know what is standard and how your equipment varies on that theme. What good is seeing the BPDU's in a trace file if you don't understand what they contain or how it relates to the problem at hand? Again, this may be looked at as a skill set issue but--expecting to solve critical problems with a packet-sniffer while not knowing this about your network is a mistake.
4) Uni-directional SPANs or Port Mirroring & Single-sided trace files.
Often the switch port used by a server you need to monitor is incapable of providing a bi-directional SPAN (Port Mirror). If so, you cannot get answers from such a trace as it will miss critical information. It can be an oversight by the Engineer doing the trace but sometimes it is simply not understood to be such a critical concern--and ignored. Either way, when you have a situation like this you need to bite the bullet and put in a Change Order to get it moved to a fully bi-directionally mirror-able port before any serious analysis can be done.
Here is a good example of why this is so. Picture a Client and a Server. The Server wants to end a specific TCP connection and keeps sending FIN's. Yet, we never see the Client send back a FIN ACK. We do see other traffic between them and know that there is connectivity. So, here are the questions:
--Are the FINs not arriving at the Client--or--is the Client receiving them and appropriately sending back the FIN ACK--which are not getting back successfully?
----If so, then it is most likely a network issue.
--Are the FINs arriving successfully--but being ignored by the Client?
---If so, then it is mostly likely a Server or OS or Data Center issue.
These questions can not be answered with a trace file that only sees one side of the conversation. Two traces, sychronized, are needed to determine the answer to these questions.
5) Incorrect filters--either Capture or Display
An important concept here is that filters add nothing--they only remove--they only filter out. When you say that you are "filtering for" what you mean is that you are "filtering out" everything else. This isn't just semantics as understanding this perspective is critical to success.
Capture Filters:
Capture Filters are irreversible. If you filtered out something that you need to see--you just aren't going to see it. There is no second chance without running the test again.
Capture Filters determine what is allowed in the Capture Buffer. If the data is there to see--great. If you filtered what you need out--you can't change the filter after the fact. A very experienced Protocol Analyst may notice the problem by seeing anomalies that amount to the shadow of the missing data--but most will not be able to tell. And, of course, even if you can tell--you still have to re-test.
This might lead you to think that you should not use Capture Filters--and that is half true. If you don't really need them--don't use them. However, if you are drinking your packets out of the Fire Hydrant--you have no choice. Under those conditions the data will fill up your Capture Buffer is less than a single second.
Another point is that they should be consistent within a Test Design. If they vary too much, they will create false differences that can easily lead the Network and Application Performance Analyst or Protocol Analyst astray.
Monitor Filters:
Monitor Filters are forgiving. They work the same way--in that they filter out, not in. However, you can change your mind. The data is in the can (trace file) and it is only a matter of changing the filter to see what was filtered out the last time. Many times I am stumped and then have an idea--go back and change my Capture Filters--and bam! There is the answer. The point is--incorrect Monitor Filters will just as easily lead you astray--but you still have the opportunity to find your way back since the data is still there.
Again, this might leave you thinking to avoid Monitor Filters. Don't even consider it. Removing irrelevant packets is required to properly measure distinct conversations and search for anomalies. In fact, understanding proper filtering is what using the packet-sniffer software is all about.
6) Lack of understanding the Packet-Sniffer’s CURRENT settings
Monday, you created a Capture Filter and left it as the default. Friday you need to capture a trace file and click on Capture. Various people perform their roles in the test and you save the trace file. Everyone goes home, back to their main job function or to bed. Then you look at it and discover that you didn't realize that the old Capture Filter was still in effect! Why? You altered the Default Capture File instead of creating a new one. Your Trace File is useless.
Always remember to review ALL settings before beginning a test. Additionally, run a practice test to make sure all filters and setting are as they should be.
Sometimes the error you discover is that you were given an incorrect IP address and that you never would find what you are looking for from the IP address from which you are capturing packets. That is a GOOD finding. It means someone's diagram is incorrect. It also means you prevented a useless round of testing.
7) Lack of test controls.
Like any proper experiment, a performance or application test requires a control group and controlled data for all groups. If it was a pharmaceutical test you might have a group with a placebo. In our field we need to create a "BESTline" first. A "Bestline" is not a baseline.
Here is an example.
You have a Client in Singapore and a Server in New York City. The client is Singapore takes 40 milliseconds to execute a transaction and European clients only need 30 milliseconds. Singapore, although farther away, has a faster connection and is expected to get it done in the same time as Europe. What now? Take a BESTline. Use a client in New York City running the same transaction in the same way on similar equipment on the same server as the other two tests. You may discover that it still takes 25 milliseconds! This may due to various issues in the Data Center, Server or PC itself, 25 milliseconds is the fastest it goes!
This means that the first 25 milliseconds have nothing to do with the transport distance or speed. It DOESN'T mean that you have to accept those 25 milliseconds. There is a great deal that can be done about it. However, it is not the network and you now know you have to focus on the Server, PC, Data Center and other components.
Such controls are easy to do--yet seldom done. That common error results in many false leads and false errors as well as lost time and money.
There are many more common mistakes......but they are the topic of different articles on http://www.InterpathTech.com.
This article is also covered in a "The Sniffer Guy" podcast--available at http://www.interpathtech.com --and--through iTunes.
1) Believing the “Intelligence” of the Software without understanding how it makes determinations.
Software default settings are very seldom correct for YOU. For example, a device may say that a SQL server should respond in 50ms. But, if that device is across a WAN with a 200ms ping time--that is highly unlikely. This causes false SLOW SQL messages. This is only an example, but there are many such alerts and messages based on default "thresholds" within this type of software tool's configuration.
Particulars of your environment may create false alerts or other messages. The definitions of what is an “excessive” delay--latency--broadcasts, etc, are up to you--not the tool.
It's important for you to know the default settings driving alerts and messages. Then, ignore or alter those alerts that are not set best--for your enterprise. Altering them to make the appropriate settings for your enterprise is the best strategy. Too many false flags or alerts numb you into ignoring important ones or--cause you to make serious errors and incorrect decisions that can be Very Very expensive.
Properly used, those features can save enormous amounts of time and show things your own eye would likely miss.
2) Not understanding the Protocols used, such as TCP, HTTP, etc.
What good is a tool that tells you information about how a protocol is behaving if you do not understand the underlying technology? By this I mean the RFC's for the protocols that are relevent to your concerns.
---What is the impact of various protocols working differently for the same application doing the same transaction--in different locations?
---What is expected according to specs--and how is your trace file showing different--or less optimal behavior?
---Why would there be 2 TCP connections from one location and 10 from another--for the same application doing the same transaction?
This short article cannot answer all these questions--but it can show you the types of information that you will need to understand in order to make sense out of the data a trace file will show you. Know the protocols well. Deep understanding of TCP is the basic price of admission. While you may consider this a matter of skill sets, my point is that attempting to troubleshooting a problem with a packet-sniffer while not understanding the protocols is a mistake--and a common one. If you add this point to the first one listed--about not believing all the standard settings on tools--you find that the tool cannot answer anything for you by itself. You need to know what you are looking at. You are the analyst--the tool is just an aid.
3) Not understanding the layer 1 and layer 2 aspects of the topology you are sniffing.
Ethernet and all other topologies have many different specifications, which are altered or outright ignored by many switch or other network device manufactures. You must know the specs and how the hardware you are working with applies those specs--or doesn’t apply them. A classic example is Spanning Tree. There are IEEE specifications for Spanning-Tree but those specifications are just a model...not a law. Each manufacturer has tweaked it in order to create some proprietary advancement to give them a competitive advantage. Sometimes, those advances become the new spec. However, you need to know what is standard and how your equipment varies on that theme. What good is seeing the BPDU's in a trace file if you don't understand what they contain or how it relates to the problem at hand? Again, this may be looked at as a skill set issue but--expecting to solve critical problems with a packet-sniffer while not knowing this about your network is a mistake.
4) Uni-directional SPANs or Port Mirroring & Single-sided trace files.
Often the switch port used by a server you need to monitor is incapable of providing a bi-directional SPAN (Port Mirror). If so, you cannot get answers from such a trace as it will miss critical information. It can be an oversight by the Engineer doing the trace but sometimes it is simply not understood to be such a critical concern--and ignored. Either way, when you have a situation like this you need to bite the bullet and put in a Change Order to get it moved to a fully bi-directionally mirror-able port before any serious analysis can be done.
Here is a good example of why this is so. Picture a Client and a Server. The Server wants to end a specific TCP connection and keeps sending FIN's. Yet, we never see the Client send back a FIN ACK. We do see other traffic between them and know that there is connectivity. So, here are the questions:
--Are the FINs not arriving at the Client--or--is the Client receiving them and appropriately sending back the FIN ACK--which are not getting back successfully?
----If so, then it is most likely a network issue.
--Are the FINs arriving successfully--but being ignored by the Client?
---If so, then it is mostly likely a Server or OS or Data Center issue.
These questions can not be answered with a trace file that only sees one side of the conversation. Two traces, sychronized, are needed to determine the answer to these questions.
5) Incorrect filters--either Capture or Display
An important concept here is that filters add nothing--they only remove--they only filter out. When you say that you are "filtering for" what you mean is that you are "filtering out" everything else. This isn't just semantics as understanding this perspective is critical to success.
Capture Filters:
Capture Filters are irreversible. If you filtered out something that you need to see--you just aren't going to see it. There is no second chance without running the test again.
Capture Filters determine what is allowed in the Capture Buffer. If the data is there to see--great. If you filtered what you need out--you can't change the filter after the fact. A very experienced Protocol Analyst may notice the problem by seeing anomalies that amount to the shadow of the missing data--but most will not be able to tell. And, of course, even if you can tell--you still have to re-test.
This might lead you to think that you should not use Capture Filters--and that is half true. If you don't really need them--don't use them. However, if you are drinking your packets out of the Fire Hydrant--you have no choice. Under those conditions the data will fill up your Capture Buffer is less than a single second.
Another point is that they should be consistent within a Test Design. If they vary too much, they will create false differences that can easily lead the Network and Application Performance Analyst or Protocol Analyst astray.
Monitor Filters:
Monitor Filters are forgiving. They work the same way--in that they filter out, not in. However, you can change your mind. The data is in the can (trace file) and it is only a matter of changing the filter to see what was filtered out the last time. Many times I am stumped and then have an idea--go back and change my Capture Filters--and bam! There is the answer. The point is--incorrect Monitor Filters will just as easily lead you astray--but you still have the opportunity to find your way back since the data is still there.
Again, this might leave you thinking to avoid Monitor Filters. Don't even consider it. Removing irrelevant packets is required to properly measure distinct conversations and search for anomalies. In fact, understanding proper filtering is what using the packet-sniffer software is all about.
6) Lack of understanding the Packet-Sniffer’s CURRENT settings
Monday, you created a Capture Filter and left it as the default. Friday you need to capture a trace file and click on Capture. Various people perform their roles in the test and you save the trace file. Everyone goes home, back to their main job function or to bed. Then you look at it and discover that you didn't realize that the old Capture Filter was still in effect! Why? You altered the Default Capture File instead of creating a new one. Your Trace File is useless.
Always remember to review ALL settings before beginning a test. Additionally, run a practice test to make sure all filters and setting are as they should be.
Sometimes the error you discover is that you were given an incorrect IP address and that you never would find what you are looking for from the IP address from which you are capturing packets. That is a GOOD finding. It means someone's diagram is incorrect. It also means you prevented a useless round of testing.
7) Lack of test controls.
Like any proper experiment, a performance or application test requires a control group and controlled data for all groups. If it was a pharmaceutical test you might have a group with a placebo. In our field we need to create a "BESTline" first. A "Bestline" is not a baseline.
Here is an example.
You have a Client in Singapore and a Server in New York City. The client is Singapore takes 40 milliseconds to execute a transaction and European clients only need 30 milliseconds. Singapore, although farther away, has a faster connection and is expected to get it done in the same time as Europe. What now? Take a BESTline. Use a client in New York City running the same transaction in the same way on similar equipment on the same server as the other two tests. You may discover that it still takes 25 milliseconds! This may due to various issues in the Data Center, Server or PC itself, 25 milliseconds is the fastest it goes!
This means that the first 25 milliseconds have nothing to do with the transport distance or speed. It DOESN'T mean that you have to accept those 25 milliseconds. There is a great deal that can be done about it. However, it is not the network and you now know you have to focus on the Server, PC, Data Center and other components.
Such controls are easy to do--yet seldom done. That common error results in many false leads and false errors as well as lost time and money.
There are many more common mistakes......but they are the topic of different articles on http://www.InterpathTech.com.
Rabu, 25 Februari 2009
The Benefits Of CRM Software
by: Dave Roth
CRM software, often called customer relationship management software, is becoming much more popular today than it was in years past. One reason for this is that more people understand what the software is and are deciding to use it. Another reason is that the software is getting better and easier to use. It has more features and benefits than it did in the past, and it is also becoming more user-friendly, which is very important. More people today are using the Internet for their businesses. As this trend continues to grow, there will be a larger need for CRM software, but only if it is found to be useful and compatible with the needs that a business owner or manager has.
There are a lot of benefits to CRM software, as well. Managers can use this software to keep track of their customers and vendors and organize them in many different ways. It is unfortunate that so many people only think of CRM software as being a datebook or contact-recording type of software. It does handle these functions, but it does a great deal more than that, which is something that many business people fail to realize today when they are presented with CRM software. This CRM software can be used to record names and dates. However, it also keeps track of sales, returns, important dates such as birthdays and anniversaries. In addition, it can help to remind salespeople of their prior commitments. This keeps them from missing deadlines, meetings, the returning of phone calls, or anything else that will affect the perception of them that their clients have.
Naturally, not missing deadlines is vital to a good business relationship. In addition, the CRM software can help a client feel as though he or she matters to a business. When a client feels important and valued, repeat business is much more likely than it would otherwise be. This is great for the business, but it is also good for the clients, because everyone in the relationship benefits from the efficiency that CRM software helps to create. Without CRM software, there is a good chance that there will be more problems in the interactions that are needed between clients and businesspeople. This is not to say that CRM software eliminates all chance of problems, but it does reduce them.
Those who use CRM software can also be more organized, because it is easier for them to find what they need when it comes to their customers, their vendors, and anything else that they need to keep close track of. It allows them to return calls more promptly, send out birthday cards, and keep customer information stored in a database where it can easily be retrieved by anyone who has authorized access to it. The main benefit to customers is that almost anyone in the company can help them, at least to some degree, because they can get to their information. This benefit of CRM software is the most important one because of the ability to let customers know that they are important to the company.
CRM software, often called customer relationship management software, is becoming much more popular today than it was in years past. One reason for this is that more people understand what the software is and are deciding to use it. Another reason is that the software is getting better and easier to use. It has more features and benefits than it did in the past, and it is also becoming more user-friendly, which is very important. More people today are using the Internet for their businesses. As this trend continues to grow, there will be a larger need for CRM software, but only if it is found to be useful and compatible with the needs that a business owner or manager has.
There are a lot of benefits to CRM software, as well. Managers can use this software to keep track of their customers and vendors and organize them in many different ways. It is unfortunate that so many people only think of CRM software as being a datebook or contact-recording type of software. It does handle these functions, but it does a great deal more than that, which is something that many business people fail to realize today when they are presented with CRM software. This CRM software can be used to record names and dates. However, it also keeps track of sales, returns, important dates such as birthdays and anniversaries. In addition, it can help to remind salespeople of their prior commitments. This keeps them from missing deadlines, meetings, the returning of phone calls, or anything else that will affect the perception of them that their clients have.
Naturally, not missing deadlines is vital to a good business relationship. In addition, the CRM software can help a client feel as though he or she matters to a business. When a client feels important and valued, repeat business is much more likely than it would otherwise be. This is great for the business, but it is also good for the clients, because everyone in the relationship benefits from the efficiency that CRM software helps to create. Without CRM software, there is a good chance that there will be more problems in the interactions that are needed between clients and businesspeople. This is not to say that CRM software eliminates all chance of problems, but it does reduce them.
Those who use CRM software can also be more organized, because it is easier for them to find what they need when it comes to their customers, their vendors, and anything else that they need to keep close track of. It allows them to return calls more promptly, send out birthday cards, and keep customer information stored in a database where it can easily be retrieved by anyone who has authorized access to it. The main benefit to customers is that almost anyone in the company can help them, at least to some degree, because they can get to their information. This benefit of CRM software is the most important one because of the ability to let customers know that they are important to the company.
Minggu, 22 Februari 2009
CCNA, CCENT, Network+, And Security+ Practice Questions: TCP, UDP, Smurf Attacks, And More!
by: Chris Bryant, CCIE #12933
Let’s test your knowledge of UDP, TCP, smurf attacks, EIGRP, and more with these questions designed to help you prepare for success on your CCENT, CCNA, CCNP, Network+, and Security+ certification exams!
CCENT Certification / Network+ Certification:
Which of the following protocols runs on both UDP and TCP?
A. DHCP
B. SNMP
C. DNS
D. ARP
E. Inverse ARP
Answer: C. DNS runs on port 53, both on TCP and UDP.
Security+ Certification:
Briefly define the term "smurf attack". (Not too briefly, though!)
Answer: Basically, a smurf attack involves sends ICMP Echo packets (pings) with the intended victim's IP address specified as the source of the Echo packets. This transmission takes the form of a directed broadcast, which means that quite a few hosts can receive it - and then respond with ICMP Echo Replies, which will all be sent to the intended victim.
CCNA Exam:
R1 and R3 are directly connected at their respective Serial1 interfaces via a DTE/DCE cable. What command will tell you whether the interface is connected to the DTE or DCE end of the cable?
Answer: Run show controller serial 1 on either router - the DTE / DCE information is near the top of the output.
CCNP Certification / BSCI Exam:
DUAL has discovered four possible paths to a remote network, with the following metrics: PathA, 1500. PathB, 1500. PathC, 2600. PathD, 3100. What command will allow EIGRP to use the first three paths without using the fourth?
Answer: variance 2 would do the job. Any path with a metric of 3000 or lower will be utilized; setting it to 3 would bring PathD into the equation.
CCNP Certification / BCMSN Exam:
What is the main purpose of IEEE 802.3ac?
Answer: The IEEE 802.3ac standard allows the maximum frame length to be extended to 1522 bytes, which means the dot1q 4-byte header doesn't cause problems in transmission.
CCNP Certification / ONT Exam:
Which queueing strategy gives priority to interactive, low-bandwidth communications by default?
Answer: Weighted Fair Queueing (WFQ) gives priority to interactive, low-bandwidth conversations, and then splits the remaining bandwidth fairly among the remaining conversations.
Look for a new set of Cisco and CompTIA certification exam questions soon!
Let’s test your knowledge of UDP, TCP, smurf attacks, EIGRP, and more with these questions designed to help you prepare for success on your CCENT, CCNA, CCNP, Network+, and Security+ certification exams!
CCENT Certification / Network+ Certification:
Which of the following protocols runs on both UDP and TCP?
A. DHCP
B. SNMP
C. DNS
D. ARP
E. Inverse ARP
Answer: C. DNS runs on port 53, both on TCP and UDP.
Security+ Certification:
Briefly define the term "smurf attack". (Not too briefly, though!)
Answer: Basically, a smurf attack involves sends ICMP Echo packets (pings) with the intended victim's IP address specified as the source of the Echo packets. This transmission takes the form of a directed broadcast, which means that quite a few hosts can receive it - and then respond with ICMP Echo Replies, which will all be sent to the intended victim.
CCNA Exam:
R1 and R3 are directly connected at their respective Serial1 interfaces via a DTE/DCE cable. What command will tell you whether the interface is connected to the DTE or DCE end of the cable?
Answer: Run show controller serial 1 on either router - the DTE / DCE information is near the top of the output.
CCNP Certification / BSCI Exam:
DUAL has discovered four possible paths to a remote network, with the following metrics: PathA, 1500. PathB, 1500. PathC, 2600. PathD, 3100. What command will allow EIGRP to use the first three paths without using the fourth?
Answer: variance 2 would do the job. Any path with a metric of 3000 or lower will be utilized; setting it to 3 would bring PathD into the equation.
CCNP Certification / BCMSN Exam:
What is the main purpose of IEEE 802.3ac?
Answer: The IEEE 802.3ac standard allows the maximum frame length to be extended to 1522 bytes, which means the dot1q 4-byte header doesn't cause problems in transmission.
CCNP Certification / ONT Exam:
Which queueing strategy gives priority to interactive, low-bandwidth communications by default?
Answer: Weighted Fair Queueing (WFQ) gives priority to interactive, low-bandwidth conversations, and then splits the remaining bandwidth fairly among the remaining conversations.
Look for a new set of Cisco and CompTIA certification exam questions soon!
Cisco CCNA, CCENT, CCNP, And CompTIA Questions: HSRP, OSPF Cost, Route Summarization, And More!
by: Chris Bryant, CCIE #12933
Let's test your knowledge of important CCNA, CCENT, CCNP, and Network+ exam topics!
CCNA Certification:
The term used for an OSPF path metric is ____________ .
Extra credit: What formula does OSPF use to calculate that metric?
Answer: OSPF's metric is referred to as cost, and the calculation is 100,000,000 / interface speed in bps.
Cisco CCENT / CompTIA Network+ Question:
Which of the following do TCP and UDP headers have in common?
A. sequence number
B. source port
C. source IP address
D. window
E. destination port
F. destination IP address
G. ACK bit
H. reset bit
Answer: B, E. In addition to the source port and destination port numbers, the UDP and TCP headers also have a checksum field in common.
CCNP Certification / BSCI Exam:
In ISIS, what is the most efficient point of a network at which to perform route summarization?
A. An L1 router.
B. An L2 router.
C. An L1/L2 router.
D. A DIS router.
Answer: C. L1/L2 routers are area boundary routers in ISIS, and this is the most efficient point at which to configure route summarization
CCNP Certification / BCMSN Exam:
Short answer: An HSRP router is the primary router and it has a priority of 100. Another router comes online in the same group and it has a priority of 107. Does the new router become the primary? If so, why? If not, what additional configuration is needed to make it the primary?
Answer. By default, the new router with the higher priority will not become the primary router. To allow a router with a higher priority to take over the role of HSRP primary from an existing and normally functioning primary, the preempt option must be configured on the router with the higher priority.
Let's use a two-router HSRP deployment as an example. R2 is the standby, R3 is the primary ("active"), and both have an HSRP priority of 100. Raising R2's priority to 150 does not automatically make it the primary, as shown below.
R2(config)#interface ethernet0
R2(config-if)#standby 5 priority 150
R2#show standby
Ethernet0 - Group 5
Local state is Standby, priority 150
Hellotime 4 sec, holdtime 12 sec Next hello sent in 0.896
Virtual IP address is 172.12.23.10 configured
Active router is 172.12.23.3, priority 100 expires in 8.072
Standby router is local 1 state changes, last state change 00:14:24
R2 now has a higher priority, but R3 is still the active router. R2 will not take over as the HSRP primary until R3 goes down - OR the preempt option is configured on R2.
R2(config-if)#standby 5 priority 150 preempt
1d11h: %STANDBY-6-STATECHANGE: Ethernet0 Group 5 state Standby -> Active
R2#show standby
Ethernet0 - Group 5
Local state is Active, priority 150, may preempt
Hellotime 4 sec, holdtime 12 sec Next hello sent in 1.844
Virtual IP address is 172.12.23.10 configured
Active router is local
Standby router is 172.12.23.3 expires in 10.204
Virtual mac address is 0000.0c07.ac05 2 state changes, last state change 00:00:13
That's enough for today! Look for more free Cisco and CompTIA certification exam questions on this website soon! A+ certification and Microsoft Vista certification practice questions are on the way as well!
|
|
 |
Let's test your knowledge of important CCNA, CCENT, CCNP, and Network+ exam topics!
CCNA Certification:
The term used for an OSPF path metric is ____________ .
Extra credit: What formula does OSPF use to calculate that metric?
Answer: OSPF's metric is referred to as cost, and the calculation is 100,000,000 / interface speed in bps.
Cisco CCENT / CompTIA Network+ Question:
Which of the following do TCP and UDP headers have in common?
A. sequence number
B. source port
C. source IP address
D. window
E. destination port
F. destination IP address
G. ACK bit
H. reset bit
Answer: B, E. In addition to the source port and destination port numbers, the UDP and TCP headers also have a checksum field in common.
CCNP Certification / BSCI Exam:
In ISIS, what is the most efficient point of a network at which to perform route summarization?
A. An L1 router.
B. An L2 router.
C. An L1/L2 router.
D. A DIS router.
Answer: C. L1/L2 routers are area boundary routers in ISIS, and this is the most efficient point at which to configure route summarization
CCNP Certification / BCMSN Exam:
Short answer: An HSRP router is the primary router and it has a priority of 100. Another router comes online in the same group and it has a priority of 107. Does the new router become the primary? If so, why? If not, what additional configuration is needed to make it the primary?
Answer. By default, the new router with the higher priority will not become the primary router. To allow a router with a higher priority to take over the role of HSRP primary from an existing and normally functioning primary, the preempt option must be configured on the router with the higher priority.
Let's use a two-router HSRP deployment as an example. R2 is the standby, R3 is the primary ("active"), and both have an HSRP priority of 100. Raising R2's priority to 150 does not automatically make it the primary, as shown below.
R2(config)#interface ethernet0
R2(config-if)#standby 5 priority 150
R2#show standby
Ethernet0 - Group 5
Local state is Standby, priority 150
Hellotime 4 sec, holdtime 12 sec Next hello sent in 0.896
Virtual IP address is 172.12.23.10 configured
Active router is 172.12.23.3, priority 100 expires in 8.072
Standby router is local 1 state changes, last state change 00:14:24
R2 now has a higher priority, but R3 is still the active router. R2 will not take over as the HSRP primary until R3 goes down - OR the preempt option is configured on R2.
R2(config-if)#standby 5 priority 150 preempt
1d11h: %STANDBY-6-STATECHANGE: Ethernet0 Group 5 state Standby -> Active
R2#show standby
Ethernet0 - Group 5
Local state is Active, priority 150, may preempt
Hellotime 4 sec, holdtime 12 sec Next hello sent in 1.844
Virtual IP address is 172.12.23.10 configured
Active router is local
Standby router is 172.12.23.3 expires in 10.204
Virtual mac address is 0000.0c07.ac05 2 state changes, last state change 00:00:13
That's enough for today! Look for more free Cisco and CompTIA certification exam questions on this website soon! A+ certification and Microsoft Vista certification practice questions are on the way as well!
Cisco CCNA, CCENT, And CCNP Home Lab Study: The DTE/DCE Cable
More Cisco CCNA, CCENT, and CCNP candidates than ever before are putting together their own home labs for their certification exam study, and that's a great trend - there's nothing like learning on the real thing!
Part of putting a home lab together is getting the right cables and understanding their usage. In this new Cisco home lab series, we'll take a look at the different cable types and how each fits into your home lab. The first cable type we'll look at is the multi-purpose DTE/DCE cable.
When I say "multi-purpose", I mean that while the cable will always perform the same task, it can be used in several different points in your home lab network. If you're going to have a frame relay switch - and you should get one if at all possible, since having your own frame relay cloud is a tremendous boost to your home lab studies and your exam score - you're going to need a DTE/DCE cable.
You can also use a DTE/DCE cable to directly connect two Cisco router serial interfaces and configure HDLC (the default) or PPP encapsulation over that point-to-point link.
Most of today's DTE/DCE cables have "DTE" clearly stamped on one end of the cable - actually, "DTE" is probably embedded into the connector itself. Naturally, the other end will have "DCE" clearly indicated. It's the DCE end that will connect to your frame relay switch. If you're going to use a direct connection to run PPP or HDLC, it almost doesn't matter which end of the cable is connected to a given router.
Keyword: "almost". You must use the clockrate command on the DCE end of the connection in order to bring the line protocol up.
If you're not sure which end of your DTE/DCE cable is connected to a given serial interface, just use the show controller serial command to get that information. Most of the output of that command isn't comprehensible, but what we need is right on top:
R3#show controller serial 1
HD unit 1, idb = 0x11B4DC, driver structure at 0x121868
buffer size 1524 HD unit 1, V.35 DCE cable
Naturally, if it's the DTE end, you'll see "DTE" there. And if you don't have anything connected to that interface, you'll see "no cable".
Whether you have your own frame relay switch or not, you'll want to pick up some DTE/DCE cables for direct connections between your Cisco home lab router's serial interfaces. Just don't forget to put the clockrate command on the DCE end of the cable! And if you're not familiar with a frame relay switch, check this same website soon for a tutorial that will show you how to set one up.
Just about any Cisco router can serve as a home lab frame relay switch, and once you've got it configured, you're in good shape - but it can be a little maddening to get it up and running in the first place. I'll show you how to avoid that aggravation in the next installment of this Cisco home lab tutorial series!
Part of putting a home lab together is getting the right cables and understanding their usage. In this new Cisco home lab series, we'll take a look at the different cable types and how each fits into your home lab. The first cable type we'll look at is the multi-purpose DTE/DCE cable.
When I say "multi-purpose", I mean that while the cable will always perform the same task, it can be used in several different points in your home lab network. If you're going to have a frame relay switch - and you should get one if at all possible, since having your own frame relay cloud is a tremendous boost to your home lab studies and your exam score - you're going to need a DTE/DCE cable.
You can also use a DTE/DCE cable to directly connect two Cisco router serial interfaces and configure HDLC (the default) or PPP encapsulation over that point-to-point link.
Most of today's DTE/DCE cables have "DTE" clearly stamped on one end of the cable - actually, "DTE" is probably embedded into the connector itself. Naturally, the other end will have "DCE" clearly indicated. It's the DCE end that will connect to your frame relay switch. If you're going to use a direct connection to run PPP or HDLC, it almost doesn't matter which end of the cable is connected to a given router.
Keyword: "almost". You must use the clockrate command on the DCE end of the connection in order to bring the line protocol up.
If you're not sure which end of your DTE/DCE cable is connected to a given serial interface, just use the show controller serial command to get that information. Most of the output of that command isn't comprehensible, but what we need is right on top:
R3#show controller serial 1
HD unit 1, idb = 0x11B4DC, driver structure at 0x121868
buffer size 1524 HD unit 1, V.35 DCE cable
Naturally, if it's the DTE end, you'll see "DTE" there. And if you don't have anything connected to that interface, you'll see "no cable".
Whether you have your own frame relay switch or not, you'll want to pick up some DTE/DCE cables for direct connections between your Cisco home lab router's serial interfaces. Just don't forget to put the clockrate command on the DCE end of the cable! And if you're not familiar with a frame relay switch, check this same website soon for a tutorial that will show you how to set one up.
Just about any Cisco router can serve as a home lab frame relay switch, and once you've got it configured, you're in good shape - but it can be a little maddening to get it up and running in the first place. I'll show you how to avoid that aggravation in the next installment of this Cisco home lab tutorial series!
Minggu, 08 Februari 2009
Cashing in by Blogging
by: Len Hutton
Believe it or not, but it’s actually possible to make money from blogging. One teenager has, in fact, earned $5,000 a month just from making posts on his blog! Of course, not every blogger is this lucky. It does take some skill, and some luck to make money from blogging. What it also takes is some knowledge of how exactly to generate income just by posting blogs. In this newsletter, we will go over three specific methods of making money on your blog: Adsense, Pay Per Lead, and Affiliate Links.
So how exactly do I make money on my blog?
You do it by working with another company that wants to use your blog as a form of advertising. It sounds like selling out, right? Not exactly. The advertising can be as in your face or subtle as you want. And it can still make you money, provided you have enough visitors to your blog.
What is Adsense?
Adsense is a program offered by Google. The program, if installed, will display ads provided by Google.
How do I get Adsense?
You’ll need to go to Google.com, first. At the bottom of the screen is a link for “Advertising Programs”. Click on that. Then click on the link for “Adsense”. Scroll down on the page that comes up and click “Click Here To Apply!” You then fill out the form with information about yourself. After 12-48 hours, Google will notify you via email whether or not your site has been accepted. When you’ve been accepted, set up your ads by doing either of the following:
1. If your blog is hosted on Blogger.com, you can set up your AdSense ads by going to your profile, selecting settings>template>add an element. Then select AdSense and login with your account info. Next, you’ll configure your ads and save the template. That’s it.
2. If you are self-hosting your blog, you’ll have to set up AdSense in more of a manual way. You’ll create your ads(which can be as small or as tall as you want) and then copy the HTML/Javascript code Google gives you. Then you’ll paste it into your blog(on the left, right, or top of the screen).
For the first few days, the ads displayed by Google will be Public Service Announcements. After the ads have been up a few days, though, the ads will switch to ads that are relevant to your blog.
How does Adsense work?
Every time a visitor clicks an Adsense ad, you get a little bit of money(usually around 30-60 cents). The amount you get for each ad clicked depends on the number of unique visitors you receive on your blog. The more visitors, the more money that can be earned.
Google will then send a check or pay you through Paypal once you’ve made at least $100 from the ads.
It is important to remember that Google will penalize you if you click your own ads, or if you ask visitors specifically to click ads. So don’t do that!
Pay Per Click
Pay Per Click is basically just like AdSense, except you don’t just work with Google—you work with multiple companies. BidVertiser is one such company you can sign up with to do Pay Per Click advertising.
How do I get Pay Per Click
You sign up with a site like Bidvertiser and then follow their instructions to set up the Pay Per Click ads on your site.
How does Pay Per Click work?
It works by paying you money each time someone clicks an ad that you display. You won’t get paid for multiple clicks from the same user in the same visitor, nor will you get paid for someone simply visiting your site. You only get paid for legitimate clicks.
Affiliate Links
Affiliate links are basically links which people pay you for. Companies will actually pay owners of popular blogs to post links on their blog. You can do as much Affiliate linking as you want.
How do I get Affiliate Links?
You can get Affiliate links by searching for “Affiliate Link Programs” on the internet. Once you find an Affiliate link program that looks good to you, sign up for it. Then you can follow their instructions for putting the link(s) on your blog.
How do Affiliate Links work?
Like the other two methods mentioned above, Affiliate links work by paying you money each time they are clicked. You get paid for each click per unique visitor.
So that’s it. There’s three legitimate ways to make money from blogging. It is important to keep in mind that the amount of money you are able to make depends on how many visitors your blog draws. If you draw a lot, you’ll make a lot. If not, the money you earn will be modest. But it’s still extra money, so why not do it?
Making money using Adsense, Pay Per Click or Affiliate Link programs is easy and effective. Start monetizing your blog today!
|
|
 |
Believe it or not, but it’s actually possible to make money from blogging. One teenager has, in fact, earned $5,000 a month just from making posts on his blog! Of course, not every blogger is this lucky. It does take some skill, and some luck to make money from blogging. What it also takes is some knowledge of how exactly to generate income just by posting blogs. In this newsletter, we will go over three specific methods of making money on your blog: Adsense, Pay Per Lead, and Affiliate Links.
So how exactly do I make money on my blog?
You do it by working with another company that wants to use your blog as a form of advertising. It sounds like selling out, right? Not exactly. The advertising can be as in your face or subtle as you want. And it can still make you money, provided you have enough visitors to your blog.
What is Adsense?
Adsense is a program offered by Google. The program, if installed, will display ads provided by Google.
How do I get Adsense?
You’ll need to go to Google.com, first. At the bottom of the screen is a link for “Advertising Programs”. Click on that. Then click on the link for “Adsense”. Scroll down on the page that comes up and click “Click Here To Apply!” You then fill out the form with information about yourself. After 12-48 hours, Google will notify you via email whether or not your site has been accepted. When you’ve been accepted, set up your ads by doing either of the following:
1. If your blog is hosted on Blogger.com, you can set up your AdSense ads by going to your profile, selecting settings>template>add an element. Then select AdSense and login with your account info. Next, you’ll configure your ads and save the template. That’s it.
2. If you are self-hosting your blog, you’ll have to set up AdSense in more of a manual way. You’ll create your ads(which can be as small or as tall as you want) and then copy the HTML/Javascript code Google gives you. Then you’ll paste it into your blog(on the left, right, or top of the screen).
For the first few days, the ads displayed by Google will be Public Service Announcements. After the ads have been up a few days, though, the ads will switch to ads that are relevant to your blog.
How does Adsense work?
Every time a visitor clicks an Adsense ad, you get a little bit of money(usually around 30-60 cents). The amount you get for each ad clicked depends on the number of unique visitors you receive on your blog. The more visitors, the more money that can be earned.
Google will then send a check or pay you through Paypal once you’ve made at least $100 from the ads.
It is important to remember that Google will penalize you if you click your own ads, or if you ask visitors specifically to click ads. So don’t do that!
Pay Per Click
Pay Per Click is basically just like AdSense, except you don’t just work with Google—you work with multiple companies. BidVertiser is one such company you can sign up with to do Pay Per Click advertising.
How do I get Pay Per Click
You sign up with a site like Bidvertiser and then follow their instructions to set up the Pay Per Click ads on your site.
How does Pay Per Click work?
It works by paying you money each time someone clicks an ad that you display. You won’t get paid for multiple clicks from the same user in the same visitor, nor will you get paid for someone simply visiting your site. You only get paid for legitimate clicks.
Affiliate Links
Affiliate links are basically links which people pay you for. Companies will actually pay owners of popular blogs to post links on their blog. You can do as much Affiliate linking as you want.
How do I get Affiliate Links?
You can get Affiliate links by searching for “Affiliate Link Programs” on the internet. Once you find an Affiliate link program that looks good to you, sign up for it. Then you can follow their instructions for putting the link(s) on your blog.
How do Affiliate Links work?
Like the other two methods mentioned above, Affiliate links work by paying you money each time they are clicked. You get paid for each click per unique visitor.
So that’s it. There’s three legitimate ways to make money from blogging. It is important to keep in mind that the amount of money you are able to make depends on how many visitors your blog draws. If you draw a lot, you’ll make a lot. If not, the money you earn will be modest. But it’s still extra money, so why not do it?
Making money using Adsense, Pay Per Click or Affiliate Link programs is easy and effective. Start monetizing your blog today!
Langganan:
Postingan (Atom)