Just starting to delve into Dojo for S3Ajax, thanks to the promise of `dojo.storage` for stashing security credentials locally. And, that Rich Text Editor doesn't look shabby either.

I'm having trouble using `dojo.io`, though. I'm a little fuzzy on the cross-browser availability of PUT and DELETE methods in XMLHttpRequest objects. So, I assume that's why `dojo.io` doesn't seem to allow them.

Code I had working stopped once I swapped over to Dojo's AJAX stuff, which I seemed to root out in the `canHandle` function of `dojo.io.XMLHTTPTransport`.

So, for now, I'm still rolling my own there.

Archived Comments

  • Yeah, Safari has trouble with PUTs, and some browsers don't support DELETE; this is why dojo.io only supports POSTS and GETs. I now model all PUTs as POSTs for this reason (including that mobile devices have trouble with wierd http verbs sometimes).

    Your S3 work looks cool! Are you getting to use the new dojo.storage I just posted? It's new and improved! Also, have you played with Moxie? It would be cool to hook that up to S3, and have it sync its local files with S3 once you are online.

  • I have gotten dojo.storage working with S3Ajax pretty well. Although the S3 wiki is anonymous and public-write, I do have code that can use dojo.storage to stash the S3 security credentials locally and then attempt to auto-recall them at page load:


    My approach to waiting for availability of the data after page load is a bit awkward, though:


    And the only other thing I have with it is that I'd like a version that doesn't require the whole of Dojo, if all I need it the storage bit. I've been trying to keep S3Ajax as focused and free of external dependencies as possible. On the other hand, when used in building an actual application, I suppose I will be reaching for things like the Dojo rich text editor and the like.