[gupnp] commit 7ebd4453f6377ed3c721b3af253cbef423bab0cc

[Sven Neumann <s neumann raumfeld com>]

Hi Zeeshan Ali,

we finally managed to update our GUPNP stack to the latest released
versions. Most things are working nicely again. But we found a problem
with the initial state events from a UPNP service. The event in question
is from a ConnectionManager service which has three evented state
variables. The event looks like this:

<?xml version="1.0"?>
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
  <e:property>
    <SinkProtocolInfo>http-get:*:application/ogg</SinkProtocolInfo>
    <SourceProtocolInfo/>
    <CurrentConnectionIDs>0</CurrentConnectionIDs>
  </e:property>
</e:propertyset>

Unfortunately the GUPnPServiceProxy object only gets the notification of
the first variable (SinkProtocolInfo). The other two state variables are
ignored. We found that this is due to this commit from you:


commit 7ebd4453f6377ed3c721b3af253cbef423bab0cc
Author: Zeeshan Ali (Khattak) <zeeshanak gnome org>
Date:   Sun Nov 15 17:29:00 2009 +0200

    Get rid of redundant loop
    
    There is only one child node inside 'property' node so no need
    to interate over all it's children nodes.


Reverting this commit fixes the issue. Can this be reverted upstream as
well ?


Thanks,
Sven

-- 
Sven Neumann
Head of Software Development

RAUMFELD GmbH | Reichenberger Str. 124 | 10999 Berlin | Germany
Tel: +49.30.340.60.98.0 | Fax: +49.30.340.60.98.99 | s neumann raumfeld com


--
To unsubscribe send a mail to gupnp+unsubscribe\@o-hand.com