[coherence-dev] XBOX 360 and mutilple storage instances

[Dominik]

OK I have been digging deeper and deeper into the rabbit hole. And look what I have found. :-)

>>> class base():
...   dic = {'1':'1', '2':'2'}
...
>>> class child1(base):
...   def __init__(self):
...     self.dic.update({'1':'2'})
...
>>> class child2(base):
...   pass
...
>>> c1 = child1()
>>> c2 = child2()
>>>
>>> print c1.dic
{'1': '2', '2': '2'}
>>> print c2.dic
{'1': '2', '2': '2'}
>>>

Do you see the problem? :-)

The dic attribute from c2 is not what you would expect.
The same thing happens to the wmc_mapping dictionary.
So after all the backends are initialized we have a mixed up wmc_mapping and nobody knows what will really be mapped to what.

I have no solution/patch yet. (I need a break first. :-))
But I am pretty sure this is the cause of all my current problems.



Hi,

as I wrote twice before I try to write my own storage backend and I made quite some progress but now I am stuck again.
The problem can be reproduced with this  very simple storage backend.
If I create for example 3 instances of this backend and open all different containers on instance "test 1" with the UPnP-Inspector the console prints:
request 0
test 1
request 0
test 1
request 51
test 1
request 53
test 1
request 54
test 1
but when I try to open the video folder with my XBOX the console prints this:
request 54
test 3

So my conclusion from this is that the XBOX always makes requests on the last backend storage that has been created (in our case here "test 3")
Does this mean you can use multiple instances of the some backend storage with the XBOX 360, is there a work around for this or do I make something wrong?

cheers
Dominik



-- 
View this message in context: http://n2.nabble.com/XBOX-360-and-mutilple-storage-instances-tp2644883p2651256.html
Sent from the coherence-dev mailing list archive at Nabble.com.