Skip to main content

Search People on Web

There are various reasons why we might need to search for people, we may need to find a lost relative, an old flame, a classmate or a business contact – but if we are using a search engine such as Google or Yahoo to search for people, we have probably realized by now that it might work in some cases but in most cases it won’t.

How come the best search engines fail so miserably when it comes to people search? The answer lies in a little known but very important part of the web called “the deep web“.

Also known as “invisible web”, the term “deep web” refers to a vast repository of underlying content, such as documents in online databases that general-purpose web crawlers cannot reach. The deep web content is estimated at 500 times that of the surface web, yet has remained mostly untapped due to the limitations of traditional search engines.

Since most personal profiles, public records and other people-related documents are stored in databases and not on static web pages, most of the higher-quality information about people is simply “invisible” to a regular search engine.

Some of the site with Deep Web content are :



Deep Web query-engine find content on deep web pages that cannot be found on regular search engines. Unlike a typical search-engine, they are designed to retrieve information from the deep web, its bots interact with searchable databases and extract data, contact details and other relevant information from personal profiles, member directories, scientific publications, court records and numerous other deep-web sources.
It is not just about finding more results, it uses advanced language-analysis and ranking algorithms to bring us the most relevant bits of information about a person in a single, easy-to-read results page.

Some of such good people search engines are :

Comments

Popular posts from this blog

JUnit – Run unit test in an Sequence / Order

In JUnit, we can use @FixMethodOrder(MethodSorters.xxx) to run the test methods in a sequence or order.

import org.junit.FixMethodOrder;import org.junit.Test;import org.junit.runners.MethodSorters;importstatic org.hamcrest.CoreMatchers.is;importstatic org.junit.Assert.assertThat;//Sorts by method name@FixMethodOrder(MethodSorters.NAME_ASCENDING)publicclassExecutionOrderTest{@TestpublicvoidtestB(){assertThat(1+1,is(2));}@Testpublicvoidtest1(){assertThat(1+1,is(2));}@TestpublicvoidtestA

Create Runnable Jar - Eclipse Options

When exporting to a Runnable Jar, there are three options in eclipse Helios. Extract required libraries into JARPackage required libraries into JARCopy required libraries into sub folder next to JAR. What are differences : Extract required libraries into JAR - Extracts the actual .class files from the libraries your app uses and puts those .class files inside the runnable JAR. So, the runnable JAR will not only contain the .class files of your application, but also the .class files of all the libraries your application uses. Package required libraries into JAR - Puts the actual JAR files of the libraries into your runnable JAR. Normally, a JAR file within a JAR file cannot be loaded by the JVM. But Eclipse adds special classes to the runnable JAR to make this possible. Copy required libraries into sub folder next to JAR - Keeps the library JARs completely separate from the runnable JAR, so the runnable JAR will only contain the .class files of your application. Option #2 is convenient be…