drive-3-pp-network-webdav-iconI’ve known about the possibilities of using javascript to interact with webdav for a couple years now but I’ve never played with it..

This weekend I had a brainwave after discussing with a couple colleagues different mobile applications and how we could migrate some of the powerful features of things like Desktop Integration Suite Webdav explorer to a mobile device..

Well… tonight I started up my UCM VM… I accidentally dropped the external hd and corrupted the vm so that took me some time to fix.. sigh.. but anyway I tried it out…
I now can leverage webdav instead of the standard UCM services to interact with content held on the UCM..Pretty sweet.
It’s very basic and have hard coded the settings but as a test I connected to a folder and brought back its contents… :)

I then thought hey this is working in my browser can I port it across to my mobile device and get it to work.. .. .. hmmm

YES!!! it works.. I used Appcelerator it authenticates.. Awesome.

So what next? … Well bed I think.. so so sleepy.

Ok, next steps::

1. Leverage html5 local storage to cache folder structure for offline quick view.
2. HTML 5 Drag Drop file from local machine into a browser javascript folder structure using the new File & DD API. (Not for mobile though)
3. Setup local file system area to copy files to – for offline access accessable via browser and cached folder structure.
4. Setup Checkout/Checkin/download – Native or Alternative/ Sync Files and alert user if files have been updated on UCM to update local copy based on revision or checksum tool.
5. Setup Table MetaData view with dynamic headers.
6. Add search feature.
7. Integrate with Mobile Blackberry Spaces App.

Lets see how cross device compatible I can make this..

Yes, I could use the UCM services and jsonify it but hey who has used webdav via javascript? :)
Actually thinking about it the services would be better in a way as they provide all this functionality and output as json..

But it’s an excuse to try something a little bit different.. And build on the webdav RFC 2518