Next gen architecture

POST /download
(i.e. allow fully assisted downloading) - need "worker bees" close to obj store
- URL
- (opt) URL_referer
- (opt) metadata
- (opt) SW
- (opt) myhost

POST /upload
- i.e. pass thru to obj store, let webgui upload, etc

GET /file
- actually return instead of redir

flexibility
- don't assume bucket name is consistent across the board
- store buckets and what is where in db
- allow multiple servers
- allow passthru (download for me, upload to me, download via me)
- permissions (i.e. no need for seperate instances)

Database

object
- System (definetely removed at this point)
- Bucket (link to bucket table)
- Path
- UUID
- Size
- Hash
- Date
- ObjMeta
- ObjTags
- statuses
- discovered T/F
- informed T/F
- facilitated upload T/F
- completed T/F
- preinformed T/F
- deleted T/F
- self DL T/F

file
- ObjUUID
- instUUID
- URL
- URL_referer
- Metadata JSON
- UL user (becomes a link to user table)
- UL_sw
- UL_host
- mtime (orig source)
- date-indexed

user is a table

user_buck (permissions)
- can_read
- can_write
- user
- bucket

bucket
- name

buck_serv
- bucket
- server
- writable
- read_preferable
- name_on_server

server
- host
- ip
- status
- creds