Hiho,
hm...
but the only thing the workaround fixes is when the server is already
running and after that i start the host that is exporting the devies with
e.g. 500ms
delay.
But in fact it can be vice versa. The host is already running, or the server
is.
The fix doesnt change anything by the way
Can we get someone to respond from a country whose subject line response
indicator is 'MV:' for a little balance.
On Fri, 2008-07-25 at 20:28 +0200, Francesco Furfari wrote:
> Hi Daniel,
>
> I quickly read the thread because I'm back just now.
> Unfortunately the Notify callback is over TCP, s
Hi Daniel,
I quickly read the thread because I'm back just now.
Unfortunately the Notify callback is over TCP, so unless we have a
similar problem even with TCP communication, the topics you discussed
should not be applicable in your case. Nevertheless we can always have a
problem with the mes
>UPnP event are meant to be best-effort because they are meant to be
>non-critical information which if lost will be received in the next
>changing of the value or anytime the device decide to send the event.
ok...but 17 devices aren't that much...consider you export 100..200
maybe it's a solution
Ok - but if it is rememberingand not retrieving fresh values from the
network there must be another problem...
Because when i start the osgi framework all my upnp devices get
imported...ok consider they're now in there...
I start a upnp event listener...
Hmm lez consider that the first time
Hi,
As said by Richard, iPOJO provides an introspection mechanism collection
data about created instances. This introspection mechanism gives information
about service dependency resolution, used service providers... Of course,
you can have information about the instance state (valid or invalid),
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
Daniel Felsing wrote:
> I know that you're the same stefano lenzi :)
> The message was just copied from a mail directed to you and francesco.
>
>
> And what would fix my problem u think?...
> Cause you've now heard a lot by my posts..i'm curious what u think could
> solve the issue..
> Cause IF i
I know that you're the same stefano lenzi :)
The message was just copied from a mail directed to you and francesco.
And what would fix my problem u think?...
Cause you've now heard a lot by my posts..i'm curious what u think could
solve the issue..
Cause IF it is really caused by UDP messages thi
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!!
>
Thank you very much!
it's work :-) !
regards
Antonio
Richard S. Hall wrote:
>
> Assume that you have a file like "config.xml" and the structure of your
> bundle is like this:
>
> org/
>foo/
> resource/
> config.xml
>
> The only thing you need to do to make
Please Mr Lenzi...take a look at that...
Is it possible that my issue is connected to this one mentioned in the
cyberlink forum?
Stefano answered to it in the cyberlink forum!!
http://sourceforge.net/forum/forum.php?thread_id=1952657&forum_id=258158
take a look at it...is this issue already fix
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
Assume that you have a file like "config.xml" and the structure of your
bundle is like this:
org/
foo/
resource/
config.xml
The only thing you need to do to make this available for to other
bundles is put the following in your bundle's manifest:
Export-Packag
Thank you for the answer. The update works and the bundle with only a file
will be updated correctly.
But now I have another problem. I would like that the other bundles use this
file. How can I import this file, so that the others bundles can use it?
Thank you for help
Antonio
Richard S. Hall
Hi Stefano and Francesco,
Is it possible that my issue is connected to this one mentioned in the
cyberlink forum?
Stefano answered to it in the cyberlink forum!!
http://sourceforge.net/forum/forum.php?thread_id=1952657&forum_id=258158
take a look at it...is this issue already fixed in the curre
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...the upnp tester does not get notified for hours...
Kind
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 each state
variable,
indicating the curren
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
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 the following now:
Running the "upnp t
Hi Rubén,
This is not possible with DS because DS activates components
asynchronously and the state of the components is (almost) completely
unrelated to the state of the containing bundle -- except that
components may only be activated if the containing bundle is active, of
course. Failing t
Hi Sahoo,
As a workaround for this started using a special version numbering
scheme to come around this problem: Bundles are released with an even
micro number (e.g. 1.0.0 or 1.0.2 or 1.2.6) and SNAPSHOT versions have
an odd micro number (e.g. 1.0.1-SNAPSHOT, 1.2.5-SNAPSHOT).
This guarantees
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
24 matches
Mail list logo
