Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Scripting] There are no way to stop thing discovering using ThingFilter + ThingCallback #311

Closed
retamar opened this issue Mar 6, 2017 · 2 comments
Closed

[Scripting] There are no way to stop thing discovering using ThingFilter + ThingCallback #311

retamar opened this issue Mar 6, 2017 · 2 comments
Labels
Scripting

Comments

@retamar
Copy link

retamar commented Mar 6, 2017

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.
@h0ru5 h0ru5 added the Scripting label Apr 3, 2017
@h0ru5
Copy link
Contributor

h0ru5 commented Apr 3, 2017

we will this issue to the scripting repo

@zolkis zolkis mentioned this issue Apr 3, 2017
Closed
@zolkis
Copy link
Contributor

zolkis commented Apr 3, 2017

This issue was moved to w3c/wot-scripting-api#16

@mkovatsc mkovatsc closed this as completed Jul 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Scripting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@h0ru5 @mkovatsc @zolkis @retamar