|Re: New (static) channels are not shown/added for things already existing [message #1736983 is a reply to message #1735796]
||Mon, 04 July 2016 19:03
| Markus Rathgeb
Registered: August 2014
Kai, I already think about this one. Not to find a general solution for the framework but how a binding or binding developer could handle that in the develop phase.|
There is already a method to change the thing type.
WDYT, could (for a custom binding) this method work (if I refer to 'thing property' here, I assume something that is allowed to be written by the binding / thing handler and is persistent -- so, not the real thing properties):
* if there is no 'created_version'' property, it is created with the current version of the binding (so, only once)
* if the property is available and does not fit to (is lower then) the current version of the binding, the property is removed and the 'change thing type' method is called (using the same thing type but another UID)
* the thing will be created again and the handler will add created_version with the current one again.
I am only interested if this could be working while the development phase where a thing changes very frequently.
I don't know if a binding should ever remove or add channels. But IMHO it is difficult to decide.
If a handler does not send updates to a previously channel anymore, it is rather useless, but removing it could be lead perhaps to a wired user experience (User: "Hey, where is my channel now??").
Adding channels is perhaps not such a problem, but at least we do not know if a thing has been created by the DSL or something similar...
Powered by FUDForum
. Page generated in 0.02476 seconds