June 22nd 2008 | Jens C Brynildsen
According to Kyle, "flXHR implements a number of very helpful extensions to the normal XHR API. flXHR implements a consistent mechanism for timeouts of requests (forward compatible with IE8's XHR). flXHR also has an error callback mechanism (which none of the XHR's have), so the author can robustly respond to any issues a user's browser may have while using flXHR. And, flXHR uses another 'flensed' project called CheckPlayer, which does all the dirty work of checking the Flash Player plugin version, initiating auto-updates of the plugin if need-be, and doing the actual dynamic embed of the flXHR.swf asset."
flXHR is also more secure, because it relies on the server administrator providing a server-controlled policy file to allow the access or not. Script-tags and iframe workaround approaches largely happen as anonymous, non-controlled accesses of data. There's no built in mechanism for authorization, contrary to the security-first Flash uses. flXHR relies on Adobe's mature, solid security model, which I believe provides the most secure (against XSS attacks) solution available out there. There are some limitations to flXHR, but the the advantages should outweigh these in most projects.
Kyle has plans for several other useful projects as well such as flCAPTCHA (a CAPTCHA anti-spam solution), flIMAGE (shows images but prevents rightclick "stealing" of them), flACHEY (for caching of JS libraries) and more. The pages for these are just placeholders, but this is certainly a project to watch for anyone doing web development.
Read more about flXHR and the other tools at flensed.com