Thursday, March 31, 2005
Cookies vs Flash For Client Side Storage
Update: The Wall Street Journal put up a solid post about the current state of affairs of all 3rd party tracking mechanisms
for his thoughts on the cookie v flash situation brought up by ClickZ
and here's what he said.
Local Shared Objects are a great vehicle for storing persistent information for websites and applications. When we built thefunctionality into Flash Player 6, we thought of it as "Super Cookies". Unlike cookies where you are limited to 4kb and key/value pairs, LSOs let you store full objects and xml data, and up to 100kb per application, per domain.I can see how it would be abused, but don't have any specific comment on that.The only reason it requires JS is because they are presumably just using Flash Runtime to use the API, but not an actual Flash appliation, and to integrate into your HTML-based app you need to call the Flash api and pass it data via a JS script, but that is easy to do in a cross-platform, cross-browser way. Likewise, more people are building asynchronous DHTML applications butt relying on Flash's XMLSocket as a server integration layer, rather than HTTP POST.
What do you guys think?
By Jason Dowdell at 03:14 PM