Opened 13 years ago
Last modified 13 years ago
#35 closed defect (FIXED)
A workspace for processing media: "Operating table" / "workbench" etc
Reported by: | Christopher Allan Webber | Owned by: | Christopher Allan Webber |
---|---|---|---|
Priority: | minor | Milestone: | 0.0.3 |
Component: | programming | Keywords: | |
Cc: | Parent Tickets: |
Description
We have a storage backend that supports multiple media types, but it's possible that certain types of media might require local files to be processed through locally. For example, maybe we'll need to have a local copy of a movie before we do transcoding. Etc. Maybe it would be helpful to create a BasicFileStorage instance that writes to a directory either made in /tmp/ or user specified somewhere else (could default to ./user\_dev/media/operating\_table/ in the config, but if completely not found in the config, could make a temporary directory to dump things in?), but which keeps non-permanent copies of files and local instances that will allow the files to be "operated" on while moving from the queue\_storage -> public\_storage during processing.
Change History (4)
comment:2 by , 13 years ago
Status: | New → Closed |
---|
I've implemented this but not documented it in a way that other people know what I mean. Nonetheless, I think that documentation is a separate bug, one more of the "how storage is handled" documnetation type of issue.
comment:3 by , 13 years ago
Component: | → Programming |
---|
Note:
See TracTickets
for help on using tickets.