This is one building block to fix this issue. The new element makes it easy to see which distribution channels have been used and since it is a special element it can be just kept by the archive without the need to actually archive the stuff it points to.
For the actual retraction the respective channels (aka DistributionServices) are in charge of their own. They have to keep track by themselves what exactly has to be done/deleted when it comes to retraction. Hope that helps, Christoph Am 31.01.2013 um 08:59 schrieb Karen Dolan <kdo...@dce.harvard.edu>: > Tobias, > > This sounds like it would fix retracting media from a flash server > distribution, is that right? > > For instance, in our implementation, Matterhorn distributes the media file to > a mounted video directory where the flash server access the file and streams > the video via RTMP. > To retract the media, would this fix allow Matterhorn to remove the > distributed media file from the mounted video directory, ignoring the fact > that the media's distribution channel is RTMP? > > - Karen > > > On Jan 30, 2013, at 12:51 AM, Tobias Wunden <tob...@entwinemedia.com> wrote: > >> We are proposing a solution to all these problems that allows Matterhorn to >> indicate to the administrator which channels a certain MediaPackage has been >> distributed to without the need for the admin ui to have knowledge about >> specific track properties for a given distribution channel. > > _______________________________________________ > Matterhorn mailing list > Matterhorn@opencastproject.org > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > matterhorn-unsubscr...@opencastproject.org > _______________________________________________
_______________________________________________ Matterhorn mailing list Matterhorn@opencastproject.org http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email matterhorn-unsubscr...@opencastproject.org _______________________________________________