Hi,

I'm using the REST ingest endpoint heavily for uploading recordings that either failed to upload or need another processing.

So if the backport would mean that the endpoint "addMediaPackage" and "addZippedMediaPackage" are no longer available the way they used to be, that would hurt a little, at least in the beginning, till I would have found another way.

Regards, Andreas

Greg Logan schrieb am Tue, 28 Feb 2012 betreff "[Opencast Matterhorn]...":
Hi Folks,

I've run into a couple of places now where I would like to backport a
change from 1.3 to an older release but I'm not sure what our policy is.
In the first case (MH-8608) the ingest/ingest endpoint in 1.3 has a bug
which duplicates workflows.  I feel like this should be backported to
1.2 as well, but it would require adding required parameters to the REST
endpoint in question.  The second case (MH-8595) changes a REST endpoint
in the scheduling bundle so that the core can be asked to return a range
of calendar information (eg: give me the next two weeks of scheduling
info).  It does this via optional parameters rather than required
parameters, and it's more of a feature for 3rd party integration than
anything else since it won't affect anything that doesn't know those
parameters exist.

No one is *using* the ingest endpoint as far as I know, and the changes
won't break anything for the scheduling endpoints, but it was decided at
the developer meeting that this should be brought to list.  Does anyone
have any objections with me backporting these changes?  I don't like the
idea of changing the API, but at the same time I don't see a good reason
to add endpoints which do the same thing as an existing ones, but
without bugs.

G



-----------------------
[email protected]
01/58801 DW 41523
mobil: 0664/60 588 4523
TU Wien
DVR-Nummer: 0005886
-----------------------
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to