[Kde-hardware-devel] UPnP: integration with coherence

Armijn Hemel armijn at uulug.nl
Sat Nov 29 19:17:39 CET 2008


On Thu, 2008-11-27 at 17:40 -0700, Aaron J. Seigo wrote:
> On Thursday 27 November 2008, Armijn Hemel wrote:
> > Any pros/cons that you can think of?
> 
> first, python vs a c++ plugin to kded4 (hm .... should we allow python addons 
> to kded? wouldn't be hard, really)

The original plan we had was to use Jolie.

>  .. anyways, what's the overhead of this? 
> any dependencies besides Twisted? otherwise, it sounds good and it would be 
> great to leverage other's work in this area.

According to the coherence website (http://coherence.beebits.net/):

Coherence in written in Python, and currently tested against version 2.4
and 2.5
  * profits from the excellent event-driven networking framework Twisted
  * needs ElementTree for its XML processing (included in Python 2.5)
  * uses Louie for signal dispatching (included inside Coherence
    beginning with 0.5.8)
  * ConfigObj (optional with version 0.5, due to the new XML
    configuration file format)
  * Divmods Nevow (optional, for all the WebUI html, together with
    Athena for the AJAX bells and whistles)
  * ctypes (optional, included in Python 2.5, for the MediaServer file
    system backend)
  * GStreamer (optional, for the MediaRenderer backend)

The 'optional' stuff is quite optional in my view of what we need for
KDE.

I realise (or at least: assume) there is a lot of overlap with for
example Jolie.

Hm, it might be best if I first draft a plan, where I explain what needs
to be done. Any objections against ASCII art? :-)

armijn

-- 
-------------------------------------------------------------------------
armijn at uulug.nl | http://www.uulug.nl/ | UULug: Utrecht Linux Users Group
-------------------------------------------------------------------------



More information about the Kde-hardware-devel mailing list