An icon is a graphic image, a small picture or object that represents a file, program, web page, or command. Icons play an important roll in the look & feel of a web page or a desktop application. Ever since internet got it’s popularity, Icons are playing an important roll to give a great look and feel to the web pages.

Below are list of ten icon search engines, which will help you to easily find the required icons and save you the difficulty of using traditional search engines.

1. IconSeeker
   
2. IconFinder
   
3. IconSearch
   
4. IconLet
   
5. IconLook
   
6. VeryIcon
   
7. EasyIconFinder
   
   
8. IconsPedia
   
9. FindIcons
   
10. ArtistValley
    

You Know Some More? Share them with everyone by adding them in the comments.

function mul($a,$b)
{
if($b==1){return $a;}
return $a+mul($a,$b-1);
}

echo mul(5,6);

One more solution which i found is as follows. But is is using the division(/) operator.

function mul($a,$b)
{
return $a/(1/$b);
}

echo mul(15,3);

So, not to be outdone, in the weeks that followed, American scientists dug 200 meters and the headlines in the US papers read: ‘ US scientists have found traces of 2000 year old optical fibers, and have concluded that their ancestors already had advanced high-tech digital telephone 1000 years earlier than the Russians.

One week later, Indian daily newspapers reported the following:
After digging as deep as 500 meters, Indian scientists have found absolutely nothing. They have concluded that 5000 years ago, their ancestors were already using Bluetooth and Wireless technology

And those who wish to read the lyrics, check it here… Song about MVC…..Yeah, yeah, yeah

.

So, CDN is a network of servers that delivers a Web page(Mostly static contents like html pages, Images, Videos, CSS, JS etc..) to a user based on the geographic locations of the user. A CDN copies the static contents of a Web site to a network of servers that are dispersed at geographically different locations, caching the contents of the page. When a user requests a Web page that is part of a CDN, the CDN will redirect the request from the originating site’s server to a server in the CDN that is closest to the user and deliver the cached content. The CDN will also communicate with the originating server to deliver any content that has not been previously cached.

In fact, 80-90% of the end-user response time is spent downloading all the components in the page: images, stylesheets, scripts, Flash, etc. This is the Performance Golden Rule and idea behind CDN. Rather than starting with the difficult task of redesigning the application architecture to speed up the page load time, it’s better to disperse the static content. This not only achieves a bigger reduction in response times, but it’s easier.(From yahoo performance Guide.)

The closer the CDN server is to the user geographically, the faster the content will be delivered to the user. CDNs also provide protection from large surges in traffic. The process of bouncing through a CDN is nearly transparent to the user. The only way a user would know if a CDN has been accessed is if the delivered URL is different than the URL that has been requested.

Some large Internet companies like google, AOL, MSN etc.. own their own CDN, but it’s cost-effective to use a CDN service provider, such as Akamai Technologies, Mirror Image Internet, or Limelight Networks. For start-up companies and private web sites, the cost of a CDN service can be prohibitive as the underlying network mechanisam is huge cost effective, but if target audience grows larger and becomes more global, a CDN is necessary to achieve fast response times.

http://developer.yahoo.com/performance/rules.html

1. HTML 5 Reference – A official guide to HTML 5 for developers.
2. Preview of HTML 5 – An overview of HTML 5 in simple English for non-developers.
3. New in HTML 5 – This document will help you learn about tags and elements that are either new in HTML 5 or have changed since HTML 4 (the current version).
4. HTML5 Cheat Sheet – This visual cheat sheet from Woork has a list of all HTML tags and attributes supported by HTML versions 4.01 and/or 5.

Source : digital inspiration / The Best HTML5 Presentations To Help You Get Started

IE is very particular when it comes to “cross-site/cross-directory” linking in iFrames and sessions. If the iFrame contains or calls a script from a different directory then IE does not always pass the session header information. If the contents are called from another domain then absolutely it will not work.

I have eliminated the issue with some workaround. My workaround is as follows.

1. If you notice the iframe SRC in IE browser, you can see that the URL is not modifying when you move to another page. It will remain as it is and you will not be able to pass any new parameter. I have take this as an advantage and created one token and append it to the initial SRC. It is as follows.

   <iframe src=”http://www.example.com/?token=<?php echo md5(uniqueid()); ?>” > </iframe>

2. I have created a table for storing session and top of each page i am checking whether the token is exist in database. If it is not exist i am inserting it as a new entry in table. Here token is primary key and session is storing as a serialized object using php serialization function.
3. In each page i will get the same token from iframe src and i am checking the same exist in db. If exist in db fetch the serialized session, unserialize it and assign back to session.

I don’t know is there any other good solution exists other than this.

Like session HTML storage is in server and it is more useful because it doesn’t get sent to the server (less overhead), and because the fields can contain more information than a cookie.

Currently, although in theory there’s little difference with cookies, HTML5 Storage is more useful because it doesn’t get sent to the server (less overhead), and because the fields can contain more information than a cookie (this feature is untested, BTW). These two advantages are clearest when you want to set a lot of values; for instance for a preference menu.

So what is the difference between localStorage and sessionStorage

Basically sessionStorage sets fields on the browser window. When the window is closed, the session fields are lost, even if the site remains open in another window.

localStorage sets fields on the domain. Even when you close the browser, reopen it, and go back to the site, it remembers all fields in localStorage. The interesting part is that if you change a localStorage field this event fires in all windows that contain a page of your site.

Essentially, that means that the entire sessionStorage is cleared when the user closes the browser window, while localStorage will remain available forever.

PPK has written an article about this. You can find it here: http://www.quirksmode.org/blog/archives/2009/06/html5_storage_t.html

.