device: create implementation to handle MPEG-TS over HTTP input

[Saxon Milton]

We wish to utilise revid in a video forwarding service, i.e. cameras would forward data to the service and then data would be analysed and distributed to different endpoints, which could be a youtube broadcast intended to store video (less than 24hr in length, created everyday) as well as a continuous broadcast. This would require an input to revid that receives MPEG-TS data through HTTP. We could try to do an implementation of the Device interface with a service that support “recv” requests as with vidgrind.

[Saxon Milton]

After further thought, it might make sense to separate the recv request handling and the MPEG-TS processing, i.e. we have a service that deals with the recv handling and then gives the MEPG-TS data to the newly implemented “MPEG-TS input”. This way we can have a single service handling incoming recv request that can forward to the appropriate revid pipeline instances.