This article explains basics of SQL Injection with an example that shows SQL Injection, and provides methods to prevent from these attacks. As the name suggests,this attack can be done with SQL queries. Many web developers are unaware of how an attacker can tamper with the SQL queries. SQL-Injection can be done on a web application…
Category: Source code
Create your own Search Engine(Interface) using Google Custom Search API
Google Custom Search API are wonderful tools to create some awesome search engine like tools. Also if you want to add a search option to your website and customize the look and feel of your search results, Google Custom Search API serve best to you.
Ring in Spring with Stunning Lingerie from Journelle and get $25 OFF purchases of $200 or more! Use promo code: SPRING200. Offer valid 2/22/13-4/30/13. Shop Now
I have created a Real Time Search engine (I call it real time as it search as you type). I am really impressed by the speed/response of Google Search API.
I will show the code for one of the search api that I implemented in demo page. Let us see how to implement Web Search API.
In order to use Google Search API, you have to first generate a Key for you. Go to following page and signup your self for the Key.
Sign up for Google API Key
Step 2: Add HTML Container for Web Search
We will create a textbox and a button that will take input for search. And a DIV that will be populated by results:
When user will write a query and push Search button, a request will be made to Google Search using Custom Search API and the results are fetched. These results are then copied into the DIV.
The code in plain english is:
1. Create an object to connect Google Web search using class
2. Set a callback function that will get call once the results for the search are fetched.
3. Call the
execute() method with search query as argument.
4. In callback function, iterate through the results and copy it to container DIV.
Click for Online Demo
oEmbed: An Open Format Every Developer Should Know About
Most of the internet users spend their online time in creating and sharing content on internet. Sharing has became one of the most popular activity of internet users. This is attributed to formats like RSS and services like Twitter, Facebook etc. that allows user to share content with each other.
oEmbed addresses the important task of sharing and embedding information anywhere on internet. It allows developers to build applications that can easily access data from vast number of websites like youtube, flickr, google video, wordpress, wikipedia and many many more.
So what’s oEmbed? Well if you go by the definition on oEmbed’s official website:
oEmbed is a format for allowing an embedded representation of a URL on third party sites. The simple API allows a website to display embedded content (such as photos or videos) when a user posts a link to that resource, without having to parse the resource directly.
Buy 2, Get 1 Free: All 10-Ream Case Paper, including OfficeMax, Boise and Hammermill Brands
The best example of oEmbed can be Facebook’s status update feature. When you paste a youtube movie link in Facebook’s status bar, it automatically identify the link content as youtube movie and embed it in the status. Similarly you can paste any kind of content link: Flickr, Wikipedia etc.
Basics of oEmbed
In this document I will use two terms very often, consumer and provider. Consumer is the client who wants to convert a link into embedded content. And Provider is one who get the request and send the oembed response. For example, if you paste a youtube URL in Facebook’s status update, Facebook will be the consumer and Youtube will be the provider.
A consumer who wants to convert a link into content will make an HTTP request like:
and the provider, in this case Flickr will send response in JSON format:
Save $100 on HP LaserJet Pro 400 M401dn Laser Printer, only $299.99 at OfficeMax.com
Once the consumer get the response, all it has to do is to utilize the content and embed it in the page.
The consumer who is requesting for the embed content must follow some basic rules while sending request. Requests sent to the API must be HTTP GET requests, with all arguments sent as query parameters. All arguments must be urlencoded.
Following are the request parameters:
- url (required): This is the URL for which embedded content is requested
- maxwidth (optional): An optional parameter for maxwidth can be passed. Some of the content provider who support this param will send the response content accordingly. For example, Flickr may set the maxwidth of image.
- maxheight (optional): Similar to maxwidth, maxheight is an optional param.
- format (optional): By default the content provider’s response is in JSON. But consumer may want the response in other formats like XML. This parameter will determine is response format
The provider who sends the response back to consumer may send it with following parameters.
- type (required): The resource type. Valid values, along with value-specific parameters, are described below.
- version (required): The oEmbed version number. This must be 1.0.
- title (optional): A text title, describing the resource.
- author_name (optional): The name of the author/owner of the resource.
- author_url (optional): A URL for the author/owner of the resource.
- provider_name (optional): The name of the resource provider.
- provider_url (optional): The url of the resource provider.
- cache_age (optional): The suggested cache lifetime for this resource, in seconds. Consumers may choose to use this value or not.
- thumbnail_url (optional): A URL to a thumbnail image representing the resource. The thumbnail must respect any maxwidth and maxheight parameters. If this paramater is present, thumbnail_width and thumbnail_height must also be present.
- thumbnail_width (optional): The width of the optional thumbnail. If this paramater is present, thumbnail_url and thumbnail_height must also be present.
- thumbnail_height (optional): The height of the optional thumbnail. If this paramater is present, thumbnail_url and thumbnail_width must also be present.
The provider may wants to add more attributes to the response.
Letting People Know You Support oEmbed
The oEmbed providers can make their service discoverable by adding following element in HEAD for the HTML document.
The URLs contained within the href attribute should be the full oEmebed endpoint plus URL and any needed format parameter. No other request parameters should be included in this URL.
The type attribute must contain either application/json+oembed for JSON responses, or text/xml+oembed for XML.
oEmbed Demo with jQuery
Integrating oEmbed support in your application using jQuery is very easy using jQuery oEmbed plugin. Following is the source code the of demo.
The HTML Code
The jQuery Code
Enter any oEmbed supporting URL (Youtube video link or Flickr link http://www.flickr.com/photos/stuckincustoms/2035748576/) in below textbox and press Get.
oEmbed in PHP
Import this small PHP library and directly use it in your application.
oEmbed for other languages
Python oEmbed (http://code.google.com/p/python-oembed/)
You must be logged in to post a comment.