| Thing interface purpose [message #1721804] |
Sun, 31 January 2016 07:08  |
|
Is it the goal that bindings implement their version of a Thing interface? And if so, what logic/functionality should reside there?
Or should the Thing remain an abstraction, which is e.g. configured through the XML files?
|
|
|
|
| Re: Thing interface purpose [message #1721825 is a reply to message #1721823] |
Sun, 31 January 2016 16:55  |
|
So far I haven't gone into many details of the new classes that were created for SmartHome, but as I'm currently looking how to best transform some bindings from v1 to OH2/SmartHome, I'm digging in a little deeper.
And during this digging, I come across things that look strange or wrong to me when compared to my understanding of how it should work. I am raising the questions to check if either my understanding is wrong or if there is room to improve the implementation.
In this specific case, what made me doubt how it should work was the createThing method in the ThingHandlerFactory interface. The implementation of this method in the BaseThingHandlerFactory uses the ThingFactory to create the thing.
As my understanding was that bindings should not create custom things, I expected the responsible class to instantiate things would be ThingManager and not the interface that bindings should implement.
I also wasn't sure which would be the best channel to get clarity on this type of issue, the forum or Github issues. So, I have been alternating.
[Updated on: Sun, 31 January 2016 16:57] Report message to a moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.03534 seconds
] 
Search
Help
Register
Login
Home
