Mail Archive Home | oscar List | July 2004 Index
Re: Think on UPnPEventListener Implementation
- Subject: Re: Think on UPnPEventListener Implementation
- From: Stefano Lenzi <kismet@xxxxxxxxxxxx>
- Date: Tue, 20 Jul 2004 10:51:01 +0200
Matrim Cauthon wrote:|
You may, but you will disagree with the specification. I think it's
better to look at UDN but they wrote ID so...
Further investigation leaves another question
concerning the filter thing,
The application that wants to be notified can
use the filter value with any of the properties:
*UPnPDevice.UDN (? according to 25.8 but 25.14.4
says UPnPDevice.ID) The both should be the same only udn its a must, so
I would be better on relying to UPnPDevice.UDN ?
Anyway, there as you can see there're some lack in the specification
It's not so easy to parse an LDAP String and your implementation may be
slower that the FrameWork one...
So since org.osgi.framework.Filter delievers not
the extraction of certain properties I only see two ways to check
different sets of these properties.
* toString() - parse the string for the
properties and values
We use match in our implementation....
* match() - set up a reference Dictionary (with
known sets of these properties) and call match (match delivers only
true if it finds the according properties matching)
Am I missing something? Which way looks more
- Re: Think on UPnPEventListener Implementation,
Powered by MHonArc.
Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster.