On 12-06-20 06:58 AM, Tobias Wunden wrote: > Hi Ruben, > >> If I understand it correctly: >> • The scheduler will keep sending ALL the catalogs in the iCal file. >> • It's up the the CA implementations whether to send those catalogs >> back to the server or not. >> -- But this may cause data inconsistencies if the scheduled metadata is >> changed and the agent starts the recording before polling the new data from >> the scheduler. >> • Those catalogs which are sent back "overwrite" those that are kept in >> the server. > > this is from my point of view an exact summary of the proposal. > >> I've got some remarks here: >> • The synch problem explained in 2) is a more general issue. Perhaps we >> should somehow check the agent's polling time and lock changes to the >> schedules that will surely not be updated on time. In the end, it all goes >> down to the communication protocol between server and capture agent --either >> we change it completely so that the core can activelly poll the agent or we >> assume the limitations of the current model and deal with them. > > By design there is no communication between core and capture agent that is > initiated by the core, since in many cases, the capture devices will not be > reachable from the outside world (including the core).
The CA pushes its configuration to the core however, and one of the configuration items is the polling interval (at least for the reference CA). I don't know about the vendors though...
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
