Fixture and Schedule of ICC World T20, 2010

Fixtures and Schedule:

The three countries in West Indies will be hosting the competition on 2010. Guyana, St. Lucia and Barbados will be hosting all the total of 27 matches. The series will be played in same format as in 2009 T20 World Cup. The finals on May 16 2010 will be hosted by Barbados. Here is the complete fixtures and schedule of T20 World Cup 2010:

Date	Match Details	Time(GMT)	Venue
Apr 30 - Fri	Sri Lanka v New Zealand, 1st Match, Group B	17:00	Providence Stadium
Apr 30 - Fri	West Indies v Ireland, 2nd Match, Group D	21:00	Providence Stadium
May 01 - Sat	India v Afghanistan, 3rd Match, Group C	13:30	Beausejour Cricket Ground
May 01 - Sat	Pakistan v Bangladesh, 4th Match, Group A	17:30	Beausejour Cricket Ground
May 02 - Sun	South Africa v India, 5th Match, Group C	13:30	Beausejour Cricket Ground
May 02 - Sun	Pakistan v Australia, 6th Match, Group A	17:30	Beausejour Cricket Ground
May 03 - Mon	Sri Lanka v Zimbabwe, 7th Match, Group B	13:30	Providence Stadium
May 03 - Mon	West Indies v England, 8th Match, Group D	17:30	Providence Stadium
May 04 - Tue	New Zealand v Zimbabwe, 9th Match, Group B	13:30	Providence Stadium
May 04 - Tue	England v Ireland, 10th Match, Group D	17:30	Providence Stadium
May 05 - Wed	Bangladesh v Australia, 11th Match, Group A	13:30	Kensington Oval
May 05 - Wed	South Africa v Afghanistan, 12th Match, Group C	17:30	Kensington Oval
May 06 - Thu	A1 v D2, 13th Match	13:30	Kensington Oval
May 06 - Thu	C1 v B2, 14th Match	17:30	Kensington Oval
May 07 - Fri	A2 v C2, 15th Match	13:30	Kensington Oval
May 07 - Fri	B1 v D1, 16th Match	17:30	Kensington Oval
May 08 - Sat	C1 v D2, 17th Match	13:30	Kensington Oval
May 08 - Sat	A1 v B2, 18th Match	17:30	Kensington Oval
May 09 - Sun	C2 v D1, 19th Match	13:30	Kensington Oval
May 09 - Sun	B1 v A2, 20th Match	17:30	Kensington Oval
May 10 - Mon	B2 v D2, 21st Match	13:30	Beausejour Cricket Ground
May 10 - Mon	A1 v C1, 22nd Match	17:17	Beausejour Cricket Ground
May 11 - Tue	B1 v C2, 23rd Match	17:00	Beausejour Cricket Ground
May 11 - Tue	D1 v A2, 24th Match	21:00	Beausejour Cricket Ground
May 13 - Thu	1st Semi-Final	15:30	Beausejour Cricket Ground
May 14 - Fri	2nd Semi-Final	15:30	Beausejour Cricket Ground
May 16 - Sun	Final	15:00	Kensington Oval

Difference betweeen Session and Cookies

Cookies can be set to a long lifespan, which means that data stored in a cookie can be stored for months if not years. Cookies, having their data stored on the client, work smoothly when you have a cluster of web servers, whereas sessions are stored on the server, meaning in one of your web servers handles the first request, the other web servers in your cluster will not have the stored information.[1]

Sessions are stored on the server, which means clients do not have access to the information you store about them - this is particularly important if you store shopping baskets or other information you do not want you visitors to be able to edit by hand by hacking their cookies. Session data, being stored on your server, does not need to be transmitted with each page; clients just need to send an ID and the data is loaded from the local file. Finally, sessions can be any size you want because they are held on your server, whereas many web browsers have a limit on how big cookies can be to stop rogue web sites chewing up gigabytes of data with meaningless cookie information.

The main difference between cookies and sessions is that cookies are stored in the user's browser, and sessions are not. This difference determines what each is best used for[2].

A cookie can keep information in the user's browser until deleted. If a person has a login and password, this can be set as a cookie in their browser so they do not have to re-login to your website every time they visit. You can store almost anything in a browser cookie. The trouble is that a user can block cookies or delete them at any time. If, for example, your website's shopping cart utilized cookies, and a person had their browser set to block them, then they could not shop at your website.

Sessions are not reliant on the user allowing a cookie. They work instead like a token allowing access and passing information while the user has their browser open. The problem with sessions is that when you close your browser you also lose the session. So, if you had a site requiring a login, this couldn't be saved as a session like it could as a cookie, and the user would be forced to re-login every time they visit.

You can of course get the best of both worlds! Once you know what each does, you can use a combination of cookies and sessions to make your site work exactly the way you want it to.

So, as you can see, each have their own advantages, but at the end of the day it usually comes down one choice: do you want your data to work when you visitor comes back the next day? If so, then your only choice is cookies - if you have any particularly sensitive information, your best bet is to store it in a database, then use the cookie to store an ID number to reference the data. If you do not need semi-permanent data, then sessions are generally preferred, as they are a little easier to use, do not require their data to be sent in entirety with each page, and are also cleaned up as soon as your visitor closes their web browser.

Reference:

1. http://www.tuxradar.com/practicalphp/10/1/0

2. http://php.about.com/od/learnphp/qt/session_cookie.htm