Thanks! This is quite clear right now. 
I was pretty sure, that agent is receiving commands from the server, and that 
confused me a lot. 

Now I know, that server does nothing to the agents, only provides the scheduler 
and listens what agent's are doing. 

My agent will talk to: 
  -Capture Agent Admin REST Endpoint
 and:
  -Ingest REST Endpoint Docs

Now (I will probably find this out from Demo Capture Agent), will I have to 
browse Scheduler REST Endpoint?

It looks like things are simple again :D 
--sorry for bothering you than, it was just the matter of architecture: how 
it's designed.


Am I right that I need to figure out the details of endpoints from the code, or 
is it written down somewhere ?

 
> 
> The capture agent is extremely loosely coupled and
> autonomous.  We knew that there would be third party
> capture agents created, so we focused on minimal
> communication between the agent and core.  The agent
> uploads a media package using the ingest api
> (addZippedMediaPackage).  The agent decides what to
> capture and when using the scheduler api.  The agent is
> autonomous in that it polls for the schedule - the core
> doesn't tell it to start, but gives it a list of dates.
> 
> Regards,
> 
> Chris
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to