Ticket #10 (closed enhancement: fixed)

Opened 6 years ago

Last modified 6 years ago

autogenerating XML device and service descriptions

Reported by: dev Assigned to: dev
Priority: major Milestone: first public beta
Component: Coherence - across the board Version:
Keywords: Cc:

Description

Don't use the file root-device.xml or any other xml-files as a template for the description files.
Instead dynamically generate the XML on instantiating the object.

Same for the services, there use something like this 

from twisted.python import reflect

    def _listFunctions(self):
        """Return a list of the names of all service methods."""
        return reflect.prefixedMethodNames(self.__class__, 'action_')

to generate the list of available actions.

Change History

12.10.2006 15:35:30 changed by dev

(In [25]) Reverted the way the WebInterface? is handled and add some simple page-generation to allow easier browsing of the children.

Included the xml-services-descriptions directory and use the xml files therein as the source for the server services definition.

This addresses #10.

And finally added connection_manager_server.py and soap_service.py for an initial test of a server service.

12.10.2006 16:48:07 changed by dev

  • status changed from new to closed.
  • resolution set to fixed.

(In [26]) Add and integrate content_directory_server.py on the way to a working basic MediaServer.

Some of the changes in media_server.py in the device xml description generation close #10.

14.10.2006 16:17:07 changed by dev

(In [28]) Actually it is a good idea to use the correct xml files if you want to support MediaServer V2 and MediaRenderer V2 ;-)

This is an supplement to [25] and addresses #10 again.