Sunday, September 23, 2007

GUPnP Release announcements

GUPnP Tools 0.2

This release features Network Light, a UPnP-enabled software-based light bulb
that provides Switch Power and Dimming services, as defined by UPnP forum as
'DimmableLight v1.0". It is mainly intended to be a simple example of a UPnP
device based on GUPnP, and a demonstration of simplistic yet powerful GUPnP
API. It can also be used to debug generic and DimmableLight control points.

Changes to Universal Control Point in this release:

- Use of gtk stock icons wherever appropriate.
- New cool icons from Lapo Calamandrei, licensed under GPL
- Use icon from the Device, if available, to represent it.
- Subscribe to services, by default.
- Ability to copy&paste details and events.
- Lots of code cleanup and refactoring and misc fixes.

GUPnP 0.6

- Added service signal autoconnection feature in the spirit of
glade_xml_signal_autoconnect(). [Zeeshan Ali]
- Fixed various bugs related to object destruction. Fixes #500, 503.
[Jorn Baayen]
- Accept 'yes' and 'no' boolean values. [Zeeshan Ali]
- More information in error messages. [Zeeshan Ali, Jorn Baayen]
- Mark GUPnPServiceIntrospectionCallback() 'error' argument as 'const'.
[Jorn Baayen]
- Fixed gupnp_device_info_get_model_number() to return the right value.
[Zeeshan Ali]
- Moved the uuid dependency to Requires.Private, and removed the
shared-mime-data build dependency. [Jorn Baayen]
- Various other minor fixes. [Zeeshan Ali, Jorn Baayen]

Special thanks to St├ęphane Loeuillet for stress-testing the library and
discovering many bugs. (Which are all fixed in this release. :) )

GSSDP 0.4.1

- Pass the correct value to n_columns argument of gtk_list_store_new().
Fixes bug#501. [Zeeshan Ali]
- Move libsoup requirement to Requires.Private. [Jorn Baayen]
- Fix compiler warning. Fixes #421. [Priit Laes]

Downloads from:

Sunday, September 16, 2007

DAAP vs UPnP MediaServer

While I believe that Lennart's work on free implementation of Apple protocols is very important for the wide-spread acceptance of free software, I fail to see any fact(s) that could support his claims like "I believe that DAAP is the superior protocol in comparison to UPnP MediaServer". When he was visited our office for his presentation on Avahi, he claimed that Zeroconf is better than UPnP itself, his argument being that Zeroconf uses simple ASCII text files and that makes it much more compatible with other Internet protocols, while UPnP uses XML (corrections welcomed). Here are a few points for him to consider:

  • UPnP is much more than addressing and discovery: Zeroconf defines standards for the addressing and discovery of services on a network but do no define any means for description, control, event notification and presentation. While this allows the services to choose any mechanism for any or all of these, the point being that UPnP itself isn't really comparable to Zeroconf but only two of it's parts.

  • ASCII is superior to XML?: how come? Just because MS supports XML or other Internet protocols didn't choose to use it?

  • "Microsoft/Intel started to include a similar technology in UPnP, the UPnP MediaServer". Media Server is based on UPnP not part of it in any way.

  • It's pronounced GUPnP, not gUPnP (thats the logo). :)

  • GUPnP is *not* an implementation of any particular service or device but a framework to create control-points, devices and services on top of it.

  • RAOP is obviously not superior to Media Renderer as it uses modified RTSP/RTP, while Media Renderer (and Media Server) standards allow you to implement any number of protocols for streaming the media, while it mandates the HTTP protocol so all devices have at least one protocol in common. Since these technologies target streaming of non-live media between devices connected to local LAN, I really don't see any reason not to just use HTTP.
Blog moved to

I am moving my blog to so that people can comment on my blog. Nothing should change for subscribers of my blog as advogato has blog syndication feature.