G

roster entity disconnection mishandling

It seems that resources are badly handled when an entity is connected from 2 differents clients. to reproduce: - an entity Romeo on libervia.org is connected 2 times with 2 separate clients: 1 from the Libervia instance of the server, and one from a local Primitivus instance - an other entity Juliet has Romeo in its roster. - when Romeo disconnect one of the instance (e.g. Libervia one on the server), it disappears entirely when it should still be present in Juliet roster (because Primitivus instance is still connected).
id

109

author

Goffi

created

16/12/2015, 08:09

updated

16/12/2015, 08:09

labels
Primitivus
type
bug
status
queued
priority
normal
milestone
0.7
severity
normal