On 09/04/2010 05:30 PM, Bruno Girin wrote: > options. Also note that the DB only contains the meta-data so sync'ing > the DB would not actually sync the files; in addition, you may not want > to sync all the files: for instance, I don't have enough disk space on
The solution I had in mind doesn't involve any kind of "sync", since files are on NFS/Samba/whatever and database connection is made via an actual TCP-socket (ie. MySQL). This way any computer on (local) network could access the files and database simultaneously. IMO there should anyways be just one shared storage for actual files, since, as you know, it's quite huge PITA to maintain sync for multiple storages. And, a leap to the future, when shotwell is ported for ie. maemo/iphone/android the storage can't be shared (or atleast my N900 can't hold my ~150GB photo storage ;)) However, it'd be great if there was an setting for 'root directory', so if I have machine A which has NFS-mount on /mnt/Photo and machine B where that same mount is on /media/Photo I could just tell shotwell that root directory is ie. /media/Photo and everything in database would be related to that. > Of course this opens up a whole new level of complexity, such as how do > you search for a given tag across multiple stores? And should you be > able to assign your own tags to photos that are stored into a store > you're not the owner of? That'd be really neat. And with reasonable API I suppose that could be achieved as well. That's "a bit" more complex than what I had in mind, but I could use that kind of system as well. IE. I have an folder on my ~/public_html which contains photos and simple perl-wrapper around that to maintain thumbnails etc. and with that kind of API I could build 'data storage' by myself for uploading photos for that perl-thingy I have. However this (again) adds more complexity. If photos are stored on local hard drive in RAW -format and the same photo is stored to flickr in JPEG (maybe with watermark) etc, how these relations and 'duplicates' are handled? TGhat "shotwell server" is anyways a neat idea. Via that it'd be possible to access ie. scaled version of the pictures over slow WAN-link or for small devices. I'm actually not quite sure if that should even be on shotwell-project, or should there be a separate project, 'shotwell-server', so that the ease of installation for simple environment would stay the same. Anyways, the first step towards this kind of approach is (IMO) the database API. I'd be more than happy to see shared database in the first place since actual file storage is quite simple to share over LAN (and even over WAN, with obvious limitations with transfer rate etc). There's a lots of issues around the 'shotwell-server', and that's not the topic on this thread, but if there'll be more discussion around that I'll be happy to take part in that. -- Take _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
