Friday, December 4, 2009

GSSDP 0.7.1 and GUPnP 0.13.2 released!

GSSDP 0.7.1 released!

- Don't leak target regex.
- Make GSSDPClient ignore Point to Point interfaces.
- Use SO_REUSEPORT if present. Darwin and some BSDs don't have SO_REUSEADDR, but
  SO_REUSEPORT.
- If we can't create a request socket don't try to create a multicast socket.
- Have specific GError code for interfaces without an IP address.
- Actually remove gssdp_client_new_full().

Bugs fixed:

1898 - GSSDPClient keeps autoselecting my VPN
1810 - Not possible to run multiple ssdp clients on darwin
1800 - leak of a gregex in gssdp-resource-browser
1796 - gssdp_client_new_full is declared in header but not implemented

All contributors:

Olivier CrĂȘte 
Ross Burton 
Iain Holmes 
Mattias Wadman 
Zeeshan Ali (Khattak) 

Download release tarballs from here

GUPnP 0.13.2 released!

Changes since 0.13.1:

- Utilize libconic (Maemo5) if available.
- Unix context manager must signal the unavailibility of all contexts when
  disposed.
- Enable silent build rules if they are available.
- Fix race-conditions in client-side notification handling.
- Unix context manager ignores point-to-point interfaces.
- Context manager ignores interfaces without IP addresses.
- Don't require timeouts to be specified in subscription requests.
- Fix build against gcc 4.[1,2].
- Make network manager thread-safe.
- Remove idle source on dispose in context manager implementations.
- Warn in docs that gupnp_service_info_get_introspection() is evil and why.
- Service retrieves introspection data in truly async way.
- Fix some leaks.
- A bunch of code clean-ups.

All contributors:

Olivier CrĂȘte 
Zeeshan Ali (Khattak) 
Ross Burton 
Jens Georg 
Cem Eliguzel 

Bugs fixed:

1890 - Timeout parsing problem with SUBSCRIBE method
1880 - subscription/notification handling is racy
1906 - Tests failed with gupnp 0.13
1849 - Compile error when using gcc 4.[1,2] and strict aliasing
1494 - Ability to deal with multiple network interfaces
1881 - networkmanager interaction should use its own dbus connection

Download release tarballs from here

4 comments:

srikieonline said...

Hello,
I am a software engineer from Bangalore, India.

I am exploring an option of writing DMP and DMC device categories.

It would be great if you could advice which approach would be better:
1. Add these services to RyGel OR
2. Add these services to over GUpnP.

Primarily I would like to know if RyGel's architecture is designed to be scaled up to implement DMP and DMC, or only suited for DMS.

THanks and Regards,
Srikanth

zeenix said...

1. DMC doesn't offer services so the choice for that should be fairly easy. :)

2. We already have one DMR implementation in rygel so all that is needed is to move some code to rygel core to make it a bit easier to implement DMR in plugins, which is waiting on intel to relicence their code. Anyway that doesn't in anyway stop you from implementing your DMR as Rygel plugin.

srikieonline said...

Thanks for your response. I was also looking for DMP implementation. Any advice on that? I had posted some more queries on the mailing list.

zeenix said...

I was also looking for DMP implementation. Any advice on that? I had posted some more queries on the mailing list.

I might be able to answer your question if you be a bit more specific. I hardly know anything about your requirements or restraints.

I strongly suggest you familiar yourself with GUPnP APIs (don't miss gupnp-av) and Rygel's plugin API and then base you decisions for both DMR and DMP on that.