Skip to content

There are no way to stop thing discovering using ThingFilter + ThingCallback #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
zolkis opened this issue Apr 3, 2017 · 3 comments
Closed
Labels
Script Management How to manage/control scripts

Comments

@zolkis
Copy link
Contributor

zolkis commented 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

@zolkis
Copy link
Contributor Author

zolkis commented Apr 3, 2017

From @h0ru5 on April 3, 2017 11:35

we will this issue to the scripting repo

@zolkis zolkis added the Script Management How to manage/control scripts label Apr 3, 2017
@zolkis 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
@zolkis
Copy link
Contributor Author

zolkis commented Apr 3, 2017

Moved the issue over from the WoT IG repo.

@zolkis
Copy link
Contributor Author

zolkis commented May 5, 2017

Fixed in #21.

@zolkis zolkis closed this as completed May 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Script Management How to manage/control scripts
Projects
None yet
Development

No branches or pull requests

1 participant