qUIpt: caching JS in window.name

Mario Heiderich has released qUIpt, a library that uses the window.name property to store away useful data, in this case JavaScript.
How does it work?
- It checks for the contents of window.name while your page is being loaded.
- If there’s nothing inside the window.name cache the JS files defined by you are fetched via XHR
- The same happens if the users enters your site for the first time of his current browser session or if document.referrer is off-domain or empty
- After that the contents of window.name are being evaluated
- If the user requests the next page on your domain the JS files are directly taken from window.name - no more requests necessary
You can check out an example of it at work
Source: Ajaxian
Original Article: http://feeds.feedburner.com/~r/ajaxian/~3/326662324/quipt-caching-js-in-windowname
qUIpt: caching JS in window.name

Mario Heiderich has released qUIpt, a library that uses the window.name property to store away useful data, in this case JavaScript.
How does it work?
- It checks for the contents of window.name while your page is being loaded.
- If there's nothing inside the window.name cache the JS files defined by you are fetched via XHR
- The same happens if the users enters your site for the first time of his current browser session or if document.referrer is off-domain or empty
- After that the contents of window.name are being evaluated
- If the user requests the next page on your domain the JS files are directly taken from window.name - no more requests necessary
You can check out an example of it at work
Source: Ajaxian » Front Page
Original Article: http://feeds.feedburner.com/~r/ajaxian/~3/326662324/quipt-caching-js-in-windowname