But I want to use gears as I know I can integrate that into air and also integrate that with a webbrowser no point in using 2 DBs to do 1 thing it would mean more work

Gears will be the central offline storage and sync tool..

You do know that there is a DB/file store within AIR. That’s kind of the point so that the app has local state so you would not need to use gears as well other than for the browser based version.

The plan is to convert the Digaset Desktop component to a desktop app with adobe AIR and use gears as the offline database and also as the localserver allowing user when they are offline to manage data and sync updates back to the UCM when they have connectivity.

At the moment I haven’t written any temp file store as I know DIS has an offline content manager. I just haven’t had the time to investigate the potential of allowing users access to archived local files when they loose connectivity via their DIS stored offline content via a web request.. but we will see. There just aren’t enough hours in the day..

Gears and air integration will be phase 2 followed by investigating a offline temp file repository

I had planned completion to be before Christmas last year and to send a copy out to Billy; however due other priorities this project was put on hold..

All interaction is done with custom idc services and json request.
It works pretty well.. Although there are a lot of bugs still to iron out..

Its also xbrowser compliant ie6.x+ and all the rest..

The planned release of the first beta will be End of July.
Integration of Air and gears planned to be complete by End of September.

The design still needs a lot of tidying..
I have also customised my json requests to only bring back required info and not the standard bulk that the UCM provides.