Changes between Initial Version and Version 1 of Ticket #2712, comment 3


Ignore:
Timestamp:
2016-01-25T14:43:44Z (9 years ago)
Author:
dawuud
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2712, comment 3

    initial v1  
    11
    2 here's our small progress, modified the Upload to upload the immutable snapshot object and mutate the user's dmd to link to it. the snapshot object so far is simply an immutable directory which links to an immutable file named "content" and N number of links to parent snapshot objects.
     2here's our small progress, modified the Uploader to upload the immutable snapshot object and mutate the user's dmd to link to it. the snapshot object so far is simply an immutable directory which links to an immutable file named "content" and N number of links to parent snapshot objects.
    33
    44https://github.com/david415/tahoe-lafs/tree/2712.immutable_snapshot_uploader.0
    55
    6 we need to persist these snapshot objects to disk. i don't think sqlite is a very good choice for this. what are some of our options to chose from other than sqlite?
     6the next step is to figure out how to persist snapshot objects to disk... though in my humble opinion we should preserve all of the Earth Dragon logic... and therefore we must store the mtime and ctime of the locally written file in addition to snapshot objects.
     7
     8the snapshot object would be any kind of blob inside the sqlite database... but it's tempting to also just make a Tahoe-LAFS object cache since it could be less code complexity to simply persist the Tahoe-LAFS cryptographic blob to disk.
     9
     10
     11I think initially we should optimize for the smallest suitable code change to magic_folder.py;
     12This modifying our existing abstract db API in magicfolderdb.py