Project

General

Profile

Forums » General »

UPnP ContentDirectory and ScheduledRecording service implementation for Tvheadend

Added by T. Wolf about 10 years ago

Hi

I'm currently developing a Python based UPnP/DLNA compatible server I would like to extend as a HTML5 based MediaCenter later on. It's called MediaProvider. Right now I'm looking to support Tvheadend as a backend for recording in ContentDirectory (UPnP) and later on for the ScheduledRecording service.

To communicate with Tvheadend I have multiple options: D-Bus, HTTP based API and HTSP

1. Is there a developer mailing list more appropiate for development questions?
2. I currently tend to use the HTTP based API (if possible) as it's JSON based. D-Bus might not be a usable solution as this is more intended for communication on the same host. HTSP is a binary protocol requiring a special implementation. Is there a formal specification beside the Python code in the github repository?

I still need to read more code to decide anything. Are there any restrictions for JSON? Is this even an intended use case for the /api/ endpoint? What about performance and feature completeness?

Thanks for your time in advance
Tobias


Replies (1)

RE: UPnP ContentDirectory and ScheduledRecording service implementation for Tvheadend - Added by Prof Yaffle about 10 years ago

IRC - freenode/#hts - is probably the place to get hold of most developers. adamsutton hangs around much of the time (although is out at the moment), as does perexg, negge, linuxstb, mpmc and some others.

    (1-1/1)