gards,
Daniel
-Ursprüngliche Nachricht-
Von: Francesco Furfari [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 25. Juli 2008 20:28
An: users@felix.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: AW: AW: AW: bug in felix upnp
basedriver 0.8 ........m-search the problem? AH ... one more note...
? Cause on apache felix
> > download page you also find 2 versions :)
> > Well...but 17 devices arent really that much if you ask me! Hmmz
> >
> >
> > Well - kind regards,
> > Daniel
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: S
ect and calls destroy on it...
:)
Kind regards,
Daniel
-Ursprüngliche Nachricht-
Von: Stefano Lenzi [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 25. Juli 2008 16:39
An: users@felix.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: AW: bug in felix upnp basedriver 0.8
m-search th
D]
Gesendet: Freitag, 25. Juli 2008 17:41
An: users@felix.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: AW: AW: bug in felix upnp basedriver
0.8 m-search the problem? AH ... one more note...
Daniel Felsing wrote:
> I know that you're the same stefano lenzi :)
> The mess
well - that are my thoughts about it,
Kind regards,
Daniel
-Ursprüngliche Nachricht-
Von: Stefano Lenzi [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 25. Juli 2008 18:12
An: users@felix.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: bug in felix upnp basedriver 0.8
m-sear
Daniel Felsing wrote:
> Hmmm...
>
> Look at osgi CMPN 111.8.1
>
> Special care must be taken with the initial subscription to events.
> According
> to the UPnP specification, when a client subscribes for notification of
> events
> for the first time, the device sends out a number of events for ea
when the refining driver
> removes the object and calls destroy on it...
>
>
> :)
>
> Kind regards,
> Daniel
>
> -Ursprüngliche Nachricht-----
> Von: Stefano Lenzi [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 25. Juli 2008 16:39
> An: users@felix.apache.
stroy on it...
:)
Kind regards,
Daniel
-Ursprüngliche Nachricht-
Von: Stefano Lenzi [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 25. Juli 2008 16:39
An: users@felix.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: AW: bug in felix upnp basedriver 0.8
m-search the problem? AH ... one mor
Daniel Felsing wrote:
> Please Mr Lenzi...take a look at that...
>
>
> Is it possible that my issue is connected to this one mentioned in the
> cyberlink forum?
Yes it is possible but only because we are speaking about the UDP
communication
>
> Stefano answered to it in the cyberlink forum!!
>
eady fixed in the current base driver
of felix?
Kind regards,
Daniel
-Ursprüngliche Nachricht-
Von: Stefano Lenzi [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 25. Juli 2008 16:02
An: users@felix.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: bug in felix upnp basedriver 0.8
....m-se
Daniel Felsing wrote:
> Just forgot...
>
> AND why do the "lost" event updates do not get propagated in future???...
>
> I can start the m-search..manually...and if there would be any states
> missing they should be delivered ANYTIME in the future...but they simply
> dont...
Because the packet c
...
Kind regards,
Daniel
-Ursprüngliche Nachricht-
Von: Stefano Lenzi [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 25. Juli 2008 12:48
An: users@felix.apache.org
Betreff: Re: AW: AW: AW: AW: AW: bug in felix upnp basedriver 0.8
....m-search the problem?
Daniel Felsing wrote:
>
AW: bug in felix upnp basedriver 0.8
....m-search the problem?
Daniel Felsing wrote:
> Nah...
> The more i look into the problem the more patterns appear in my head. ;-)
>
> In fact there is no difference...i ran tests with m-search and
without...the
> behavior can be considered t
Daniel Felsing wrote:
> Nah...
> The more i look into the problem the more patterns appear in my head. ;-)
>
> In fact there is no difference...i ran tests with m-search and without...the
> behavior can be considered the same.
> Server randomly receives no notification...
>
>
> Ok - i have tried
g, 25. Juli 2008 11:54
An: users@felix.apache.org
Betreff: Re: AW: AW: AW: AW: bug in felix upnp basedriver 0.8
....m-search the problem?
Hi Daniel,
Please look at my comments below.
Daniel Felsing wrote:
> Can it be that the "ongoing" m-search is influencing the status
notificat
Hi Daniel,
Please look at my comments below.
Daniel Felsing wrote:
> Can it be that the "ongoing" m-search is influencing the status notification
> behavior?
Yes
>
> I started a manual m-search while starting my upnp event tester on the
> server side, cause i thought maybe there was a problem
Can it be that the "ongoing" m-search is influencing the status notification
behavior?
I started a manual m-search while starting my upnp event tester on the
server side, cause i thought maybe there was a problem with some leases or
something.
But the situation got even worse. Missing devices prop
17 matches
Mail list logo