In terms of a db schema friendly to chunks, we would probably want another table and associated it with a stashed file.
Russ was discussing adding support for appending files within the swft object store application logic, so we may not have to be concerned with storing chunk references in the db? Another potential usage for a media stash is transcoding non-free formats. Here we could use the media stash as temporary location to put the media files while we transcode them. Once transcoded we could then move them into the published space. But I would not be too worried about incorporating that into the the DB schema until we get to implementation. --michael On 07/13/2011 12:30 AM, Bryan Tong Minh wrote: > Great work people! I've really been waiting for this, and I'm glad > that it has been finally implemented. > > A remark about extensibility: in the future we might want to use the > upload stash for more advanced features like asynchronous uploads and > chunked uploads. I think the database schema should already be > prepared for this, even if we're not using it. For this purpose I > would at least add us_status. Perhaps Michael has some ideas what such > a database schema should further incorporate. > > > Cheers, > Bryan _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
