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
In an execution environment where thing discovery is a long time running operation, if a device needs to find only one thing in a given type, there are no way to stop the discovery operation when first thing was found.
Using ThingDiscoveyCallback you can just ignore new discovered thing, but the lookup operations are still executing.
zolkis
changed the title
[Scripting] There are no way to stop thing discovering using ThingFilter + ThingCallback
There are no way to stop thing discovering using ThingFilter + ThingCallback
Apr 3, 2017
From @retamar on March 6, 2017 11:37
In an execution environment where thing discovery is a long time running operation, if a device needs to find only one thing in a given type, there are no way to stop the discovery operation when first thing was found.
Using ThingDiscoveyCallback you can just ignore new discovered thing, but the lookup operations are still executing.
Copied from original issue: w3c/wot#311
The text was updated successfully, but these errors were encountered: