2015-03-03, 11:56
I'm not a student but this is a project idea I've actually looked into myself a year or so ago but never had the time to really work on and I'm be happy to mentor it if a student is interested.
OhNet is a cross-platform UPnP stack provided by the OpenHome project and contains basic interfaces/implementations for all objects and resources defined in most of the UPnP specifications with an addition of OpenHome specific stuff which improves playlist handling and other things not properly covered by any UPnP specification.
Kodi relies on the Platinum UPnP SDK which has very limited possibilities to extend the existing functionality. Furthermore any extensions fixes need to be coded into code not maintained by Team Kodi. Therefore moving to a different UPnP implementation that provides a similar feature set but can be easily extended would have a high benefit for Kodi.
The main goal is to develop a UPnP ContentDirectory implementation using the OhNet UPnP stack (see a0596372c6398e1bbf7fb0534ad21d510604d2f8 for a start) either inside or separate of Kodi that supports most of the features specified in the UPnP ContentDirectory specification. An additional goal would be to make it easily extensible (think UPnP profiles and vendor-specific properties) without having to touch the actual implementation.
OhNet is a cross-platform UPnP stack provided by the OpenHome project and contains basic interfaces/implementations for all objects and resources defined in most of the UPnP specifications with an addition of OpenHome specific stuff which improves playlist handling and other things not properly covered by any UPnP specification.
Kodi relies on the Platinum UPnP SDK which has very limited possibilities to extend the existing functionality. Furthermore any extensions fixes need to be coded into code not maintained by Team Kodi. Therefore moving to a different UPnP implementation that provides a similar feature set but can be easily extended would have a high benefit for Kodi.
The main goal is to develop a UPnP ContentDirectory implementation using the OhNet UPnP stack (see a0596372c6398e1bbf7fb0534ad21d510604d2f8 for a start) either inside or separate of Kodi that supports most of the features specified in the UPnP ContentDirectory specification. An additional goal would be to make it easily extensible (think UPnP profiles and vendor-specific properties) without having to touch the actual implementation.