writes not included in getListing until pushed out to remote

[michielbdejong]

• nodes are never added to parent until they go to remote.
• that also causes inspect not to always show everything there is in the IndexedDB 'nodes' store; with following function you can see there's often much more in IndexedDB than remoteStorage.inspect() shows:

    function inspectIndexedDb () {
      var dbOpen = indexedDB.open('remotestorage', 2);
      dbOpen.onsuccess = function() {
        var db = dbOpen.result;
        var transaction = db.transaction(['nodes'], 'readonly');
        var nodes = transaction.objectStore('nodes');
        var cursorReq = nodes.openCursor();

        cursorReq.onsuccess = function() {
          var cursor = cursorReq.result;
          if(cursor) {
            console.log('node', cursor.value.path, cursor.value);
            cursor.continue();
          }
        };
        transaction.oncomplete = function() {
          console.log('done');
        };
      };

• this will mean getListing will always give empty results in anonymous mode
• and outdated/incorrect results when outgoing changes are pending

I will rewrite indexeddb.js so that it has separate meta and bodies stores instead of one nodes store, and then meta data can immediately be written into the folder listing format.

[raucao]

Attention!

We should probably best discuss via voice or on IRC. This is intended behaviour as it gives you the cached listing from the server, not the would-be listing that the server creates in the future!

[michielbdejong]

ok, i understand, but there are two problems with that:

1. it violates the 'asynchronous synchronization' principle Term: Asynchronous Synchronisation offlinefirst/research#9
2. it breaks anonymous mode (where there is no server)

[raucao]

Ok, then we just need to extend the 'cached' key with the new format. We already save everything locally there. No need to change more.

[michielbdejong]

this is the last issue blocking an 0.9.1 release. if work on #587 is suspended, then maybe an easy patch to quickfix this would be if we merge items from the changes store (which records outgoing changes) into getListing results. that's a very superficial change and would probably have the desired effect

[raucao]

Ok, sounds like a plan.

[raucao]

Fixed in 0.10.0-beta.