Friday, June 11, 2010
Fifa World cup 2010 kicks off today in South Africa. Yes, it is the first time Africa is hosting the tournament.
Looking forward to an entertaining month ahead and may the best team win.
Talk of favourites in this year's event, and names like Spain, Argentina, and England and of course the perennial favourites Brazil come up.
At our office, we did a mini Odds/Bets and I was lucky to bet on the following teams as favourites to win the tournament: Brazil, France, Paraguay, Nigeria and Australia.
At least I have Brazil on my pot :)
Wish you all the best and may the best team carry the cup!
Tuesday, June 08, 2010
Use Cookie-free Domains for Components
This is an excerpt from Yahoo Best Practices for Speeding Up Your Web SiteWhen the browser makes a request for a static image and sends cookies together with the request, the server doesn't have any use for those cookies. So they only create network traffic for no good reason. You should make sure static components are requested with cookie-free requests. Create a subdomain and host all your static components there.
If your domain is
www.example.org, you can host your static components on
static.example.org. However, if you've already set cookies on the top-level domain
example.orgas opposed to
www.example.org, then all the requests to
static.example.orgwill include those cookies. In this case, you can buy a whole new domain, host your static components there, and keep this domain cookie-free. Yahoo! uses
yimg.com, YouTube uses
ytimg.com, Amazon uses
images-amazon.comand so on.
Another benefit of hosting static components on a cookie-free domain is that some proxies might refuse to cache the components that are requested with cookies. On a related note, if you wonder if you should use example.org or www.example.org for your home page, consider the cookie impact. Omitting www leaves you no choice but to write cookies to
*.example.org, so for performance reasons it's best to use the www subdomain and write the cookies to that subdomain.
Ref: Please read here
Friday, June 04, 2010
Asp.net - Invalid postback or callback argument. Event validation is enabled using ‘
This is a common Asp.Net error when updating List Box items on the client side.
I asked this question on stackoverflow.com (Click here).
Just reflecting on how many views people have had on this question, it seems to be a common issue most Asp.Net developers encounter.