Matterhorn currently only supports scheduling events but not creating them ad-hoc. For external devices like Crestron it's not possible to easily start a capture and stop it later on by e.g. clicking a simple start/stop button.
To solve this we implemented an endpoint which is able to start (create), stop and prolong an event by a simple POST call.
Hi Greg,
I agree with you that we should updating the CA API instead of making piecemeal additions. But this didn’t happen for years and therefore in the meantime this feature was implemented to resolve that outstanding request. So I suggest we use this feature as long there is no new CA API. With the new CA API we make sure this new feature request is included in the designs as well and then we rewrite it as we do for all the other API calls.
Lukas
Am 02.09.2016 um 00:22 schrieb Greg Logan <gregorydlogan@gmail.com<gregorydlogan@gmail.com>>:
Hi folks,
Looking at MH-10342, there are additional CA API REST calls that would become available, but the existing CA API would remain unchanged - agents that are not aware of the new calls would just ignore them.
I'm of two minds with this feature: On one hand, it looks like it would work (I am currently unable to test due to my ongoing admin UI compilation issues), and it would resolve a longstanding feature request. On the other hand, we've been talking on and off about updating the CA API for years, and I feel like our efforts should go towards that rather than making piecemeal additions.
What does the community think in regards to this?
G
–
You received this message because you are subscribed to the Google Groups "Opencast Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev+unsubscribe@opencast.org<dev+unsubscribe@opencast.org>.
–
You received this message because you are subscribed to the Google Groups "Opencast Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev+unsubscribe@opencast.org.
Hi,
While I've always been an advocate to "go strictly by the book" when it
comes to modify an API, I agree with Lukas in this case. Perhaps adding
this feature is another push move the new API forward and we shouldn't
let our own inability to design a new API hinder the addition of new
features which, as Greg reminds, have been requested long ago.
Regards
–
Rubén Pérez Vázquez
Universität zu Köln
/Regionales Rechenzentrum (RRZK)/
Weyertal 121, Raum 4.05
D-50931 Köln
✆: +49-221-470-89603
–
You received this message because you are subscribed to the Google Groups "Opencast Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev+unsubscribe@opencast.org.
I think incremental feature additions to the API that are backwards-compatible are fine.
Hasn't there be a discussion at a technical meeting about this PR?
IIRC, Lukas mentioned that a proposal for this change had passed a long time ago... I think he referred to https://groups.google.com/a/opencast.org/forum/#!searchin/dev/proposal$20capture/dev/eqhQV6OSEVA/jJX9yc3eWscJ.
Best,
Sven
–
You received this message because you are subscribed to the Google Groups "Opencast Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev+unsubscribe@opencast.org.
Hi Sven,
I believe there was, and that proposal is (probably?) what was linked in
the ticket. I'm fine merging it, hopefully I can get around to it this
afternoon.
G
–
You received this message because you are subscribed to the Google Groups "Opencast Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev+unsubscribe@opencast.org.