Friday, September 30, 2005
Permanent Client-Side Storage for AJAX Applications, Part I
Just a quick note: I've pretty much finished the permanent client side storage API I've been working on for O'Reilly. It uses a hidden Flash file, wrapped with a nice JavaScript API, to give AJAX applications the ability to store long term information. I'll post a beta on Monday. It's all open source and opens up the possibility of creating some very interesting web-based applications that weren't easily possible before. I'll be using this in my AJAX consulting (including the history and bookmarking framework I created last week) if companies are interested.
Comments:
Links to this post: See links to this post
<< Home
Very interesting.
Could you dual-licensing your code as LGPL so we can use parts of it in qooxdoo? Would be a nice thing to include :)
Could you dual-licensing your code as LGPL so we can use parts of it in qooxdoo? Would be a nice thing to include :)
I have developed a cookie api earlier which I need to port to qooxdoo the next time, but cookies are somewhat complex. You can only have twenty of them for any domain and there are some size restrictions. As I know the Internet Explorer has some special storage possibilities at client side. Possible a cross storage solution (which can use different methods) is a good idea.
The storage API I have created can permanently store an arbitrary amount of information, after approval by the user. On Friday I stored 10 megabytes with no problem; it was fast and stable.
wpbasti, the code is under a BSD license so there will be no problem for you to use it in your framework.
is BSD compatible to LGPL? LGPL is more restrictive as I know. But if I get your ok - I think it will be ok. ;)
The cool thing about the IE storage layer could be that you does not must ask the user. Probably we could use cookies first, than the IE storage layer or if we need more space or the user has no IE then we use you method.
But all I can say it will be a great step it the right direction to have such storage at client side.
But all I can say it will be a great step it the right direction to have such storage at client side.
Most forms of the BSD are compatible with the GPL and LGPL. A super old version of the BSD license has something called the advertising clause, a restriction which caused it to be incompatible with the GPL. Most people now use newer versions of the BSD, which don't have this problem.
The BSD essentially says that you don't have a warranty; it's pretty simple.
The BSD essentially says that you don't have a warranty; it's pretty simple.
The method I use doesn't have to ask the user for
permission for under 100K; I have tested IE's
proprietary storage method and it can only do 60K.
Post a Comment
permission for under 100K; I have tested IE's
proprietary storage method and it can only do 60K.
Links to this post: See links to this post
<$blogbacklinktitle$>
<$blogbacklinksnippet$>
<$blogbacklinksnippet$>
<$i18npostedbybacklinkauthor$> @ <$blogbacklinkdatetime$>
<< Home
This page is powered by Blogger. Isn't yours?
Subscribe to Posts [Atom]