On 12-02-27 10:36 AM, Ruediger Rolf wrote:
To give an example this REST endpoint would have a method addTrack that has as required parameters the mediapackage-xml, the URL of the new file in the working file repository and the flavor of this track and it returns the updated mediapackage-xml with the track information inside. The data that was submited to this service is not stored anywhere, we can make sure that the XML that the service returns is valid and we could maybe add some additional benefits like checking if the URL of the new file exists in the WFR and that the path is correct etc.
How is this different from the ingest endpoints? G _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
