Hi pawel,

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
-----Original Message-----
From: Pawel Fic <[email protected]>
Sender: [email protected]
Date: Mon, 30 May 2011 05:53:03 
To: Opencast Matterhorn<[email protected]>
Reply-to: Opencast Matterhorn <[email protected]>
Subject: Re: [Opencast Matterhorn] API Spec

Well, I am still browsing the code. But I will ask some more questions;
Well this thread is a documentation, and it will probably help other people to 
understand Matterhorn architecture.

-------------------------------------
 Josh said, that I do not need /captureagent service to implement my own 
Matterhorn Capture Agent, I only need: 
 - capture-admin REST
 - ingest REST

to develop a functional capture agent.

But then:

1. 
I need my capture agent to be managed by the server (Schedule recording must 
work) - will this be possible without implementing /captureagent - rest point?

2. 
How the files are copied from capture agent to the server? 
I managed to upload files pretending to be a browser (just as "Upload a 
recording" does it) - but is how capture agent supposed to do it ? 

3. 
Well, maybe I just can't find it, but:

   /capture-admin/docs
   /ingest/docs

are not sufficient for me to develop a capture agent. ... I do not think they 
are sufficient. 
Am I right, that I have to read the source-code? 


4. 
I would know some theory about what is capture agent, and how it supposed to 
work.

I assumed, that there is a protocol between a server and capture agent 
(client), that allows the server to manage the agent's behavior, somehow 
retrieve/upload recordings from client/to server.
Now I am not sure, especially after I hear that "captureagent" REST service is 
not required. 

-Pawel


> > I want to develop a C++ capture agent. I need API for
> capture agent, capture admin, and whatever will be needed.
> > 
> > I have a brief description of REST endpoints, that is
> available on the front page of Matterhorn after it is
> installed.
> > 
> > Right now I do a live debugging of whatever demo
> capture agent is talking to Matterhorn.
> 
> The services involved are scheduling, capture-admin, and
> ingest, but *not* /captureagent.. this last service is
> provided by the Matterhorn capture agent, but is not a
> required part of the agent/server communication.
> 




_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to