You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently thread synchronization at client side was done thanks to synchronized block at LWM2M Object level (BaseObjectEnabler)
With the addition of WriteComposite(#959) and the need to apply operation at LWM2M Root Level in an atomic way and so this is probably no more enough.
We should maybe introduce a new locking interface which allow to implement different lock strategy.
This interface should provide a way get lock for a given LWM2M Node :
sbernard31
changed the title
Enhance LWM2M tree synchronizaton mecanism at client side
Enhance LWM2M tree synchronizaton mechanism at client side
Jan 29, 2021
Hmm, it looks interesting. To be honest, I've not felt like that gimmick needed for me until now, but I think introducing the lock mechanism is a good idea.
Currently thread synchronization at client side was done thanks to
synchronized
block at LWM2M Object level (BaseObjectEnabler
)With the addition of WriteComposite(#959) and the need to apply operation at LWM2M Root Level in an atomic way and so this is probably no more enough.
We should maybe introduce a new locking interface which allow to implement different lock strategy.
This interface should provide a way get lock for a given LWM2M Node :
We can imagine several implementation like :
I'm not so sure, just an idea.
Some more resources :
The text was updated successfully, but these errors were encountered: