...
TODO: What if you add a script to a FIle entity, synStore(), exit, restart and synGet()? You now have two copies of the file, one in the cache and the original elsewhere. The user would like to keep editing the original and, upon synStore(), update again. How does the client know to associate the original? One solution: Client keeps a map of <Syn FileHandle> -> <local location> which gets saved upon exit and loaded upon start-up and which 'overlays' or 'amends' the default cache mapping.
TODO: read a remote file, edit it, lose session, then repeat 'loadEntity', keep editing local file, push/store entity what should happen?
TODO: how can we download a folder hierarchy and have that hierarchy reflected in the system? One approach is to mimic the situation in which we upload a folder hierarchy, keeping pointers to files which are outside of the cache. I.e. we download the files into a folder hierarchy outside of the normal cache and keep in-memory pointers to those file locations. In this case Synapse would hold the "truth" about the hierarchy, so the user would not be allowed to move things around locally without messing up the cache.