Every single DLNA device is implemented differently, which has caused lots of frustration in our labs during development. Some devices cache folders, some query them only every few moments, and some query constantly. Some also pay attention to UPnP ContentDirectory SystemUpdateID status events, and some ignore them.

We've implemented our DLNA server in compliance with the DLNA specifications, especially regarding firing UPnP events whenever folders change, but the results from the client sides are unpredictable at best.

that's what I figured, I think I can create a work around for what I want to do though.

thanks for the reply

I'm using timespans and checking the intervals when the event is fired. If my timespan exceeds the minimum set I allow the refresh to go through, If not the items remain until the next event is fired.

it's my experience that sometimes it doesn't matter when you want to refresh the list. The PS3 and XBMC, at least, cache the folder list and when they feel like it they ask for an update. Sucks in my opinion, they should all behave the save and ask for an update whenever the user requests the folder not when they arbitrarily feel like it.

We agree wholeheartedly. Unfortunately, DLNA wasn't optimized at its inception to account for massive dynamic updates. So, most client stacks aren't quite up to snuff.

We will be adding an event to the Plugin API so that plugins can at least inform PlayOn when something has changed in their directory structure, so that DLNA clients that conform to system update notifications will do the right thing.