About timestamp: I mean the timestamps inside the ZIP package. That should never change as long as the owner of this specific package (the user) does not add, change or delete content inside the package. You can rename the ZIP file, copy it around and have other timestamps for the package itself, but the files inside the package will stay untouched.

CouchDB in't a "web-db". You can use simply a browser to administrate the DB, but you need that web-admin-interface. Probably the same as other web-tools for relational DBs like mysql.

CouchDB is a so called "Document-oriented-DB". Perfect for Poser, because Poser files are documents! Start with storing the documents as a whole and later on each figure, each actor, each material described in those documents can become a (retrivable) part (record) of the database! In contrast to a relational database the structure is not fixed.

I saw too mutch relational databases eat up the content in a crash. So maybe it is not a good idea to store files (of any sort) without backup into a relational DB. They are not made for this. Users will crucify the programmers if they loose paid content because of a DB crash. I would left it to the user to take care of the original files.

By the way: It is dead easy to link several CouchDBs with free content :) The name "Couch" says it all: It is an acronym for "cluster of unreliable commodity hardware".

---