Announcing dLeyna-renderer-0.1.3 and dLeyna-server-0.1.2
by Mark Ryan
Hi All,
The dLeyna team is pleased to announce new stable releases of
dLeyna-renderer and dLeyna-server. These new versions should be used in
conjunction with dleyna-connector-dbus-0.1.0, dleyna-core-0.1.0, and
msd-0.1.0, which have not changed.
Changes introduced in dLeyna-renderer-0.1.3
-------------------------------------------
* Fixed Bug 110: GetRenderers() should return an array of object
paths "ao" instead of an array of strings "as" (
https://github.com/01org/dleyna-renderer/issues/110 ).
- The implementation of some dLeyna-renderer methods and
signals were inconsistent with the API documentation.
This has now been rectified.
* Fixed Bug 97: dLeyna renderer can crash if renderer dissapears
(7.2.8.4,6) ( https://github.com/01org/dleyna-renderer/issues/97 ).
- This was a particularly nasty bug which could cause dLeyna-
renderer to crash under certain cirumstances during device
discovery.
* Fixed a build issue: [Build] Ship the internal library in a private
directory.
- A small fix to make packaging of dLeyna easier.
Changes introduced in dLeyna-server-0.1.2
--------------------------------------------
* Fixed a build issue: [Build] Ship the internal library in a private
directory.
- A small fix to make packaging of dLeyna easier.
The new versions can be downloaded from
https://01.org/dleyna/downloads/2013/dleyna-renderer-0.1.3-and-dleyna-ser...
Best Regards,
Mark
7 years, 6 months
New "Changed" notification and related updates
by Ludovic Ferrandis
Hi,
we are going to update the notification rule in dleyna-server.
You can follow and answer using github issue tracker here:
<https://github.com/01org/dleyna-server/issues/109>
To resume:
1 - "LastChange" notification will be remove
2 - Changed notification will be used for "LastChange" notification and
"ContainerUpdateID" notification.
The rule:
If both notifications "LastChange" and "ContainerUpdateID" exist, only
"LastChange" will be converted into "Changed" notification.
"ContainerUpdateID" will still be converted into "ContainerUpdateID"
notification.
If only "ContainerUpdateID" notification exists, it will be converted
into a "Changed" notification AND "ContainerUpdateID" notification.
When "ContainerUpdateID" is converted, ChangeType = MOD (see github for
details)
The purpose of this new signal is to have only 'one entry' for all the
notification of change that came from the server and to avoid duplicated
signals.
Ex: if a server support "LastChange" notification and
"ContainerUpdateID" notification and your application register for both,
you will receive 2 notifications on a folder change.
By using "Changed", your application will have a single way of managing
change without checking the server capabilities.
If you have any comments, you can answer here or on github.
Regards,
Ludovic
--
Ludovic Ferrandis
Open Source Technology Center
Intel Corporation
7 years, 6 months