Road Map
The projects on 4th Line.org are developed openly and released under Free Software licenses. If you'd like to contribute and participate, fork Cling source and submit pull requests in our repository and issue tracker.
Cling 2.0
-
Integration with and for CDI (IN PROGRESS)
Currently all modules (transport, protocol, registry, binding) of Cling are wired through constructor injection from a single UpnpService entry point constructor. We can keep this flexibility (easy overriding by developers of create() methods) but at the same time enable dependency injection frameworks. This is mostly adding CDI annotations on core classes and testing Cling Core with Weld.
-
Client/server profile system
Similar to what other, more media-oriented UPnP packages provide, Cling will most likely grow a profile system to help with device incompatibilities (for example, see the profile system of Serviio). This issue and the design of the profile system is under discussion on the Cling list here.
-
Providing an OSGi UPnP Device Service (IN PROGRESS)
Cling can be used to implement the OSGi UPnP Device Service specification version 1.1 as defined in the OSGi Service Platform Service Compendium (Release 4, Version 4.2 August 2009). A proof-of-concept implementation is already available here and its useful bits should be added to Cling. This issue is under discussion here.
-
Switchable XML low-level routines for Android 2.1/2.2
Android 2.1 has awful support for XML parsing and printing (broken schema support, no transformers), Android 2.2. is marginally better. Consider either dropping support for Android 2.1 and removing half-baked XML utility classes, or adding configurable low-level XML handling with automatic detection of 2.1 or 2.2.
-
GENA eventing support in the HTTP bridge
This has already been designed and needs to be implemented, see Bridge Architecture.graffle in SVN.
