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.

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

Supporting Sleepy Devices #2059

Open
egekorkan opened this issue Nov 28, 2024 · 1 comment
Open

Supporting Sleepy Devices #2059

egekorkan opened this issue Nov 28, 2024 · 1 comment
Labels
Has Use Case Potential The use case can be extracted and explained Needs discussion more discussion is needed before getting to a solution Selected for Use Case The issue is relevant for the work and should move to an use case

Comments

@egekorkan
Copy link
Contributor

Note: This should be formulated as a user story on use cases repo once the template is ready. This was a plugfest outcome presented by @mkovatsc

  • Who (As a...): Consumer Application developer
  • What (I need...): Indication that a device is sleepy and cannot be always communicated with. Ideally how often can the device be communicated with (every 10 mins etc)
  • Why (so that I can...): Handle request timeout differently and communicate only when the device is available
    • Details: Without this, an Consumer implementation simply thinks that the device is not available. It will be available at some point and the request should be sent only at that time.

See: https://github.com/w3c/wot/blob/main/PRESENTATIONS/2024-11-wot-week/Plugfest/plugfest-summary-mkovatsc.pptx

@egekorkan egekorkan added Has Use Case Potential The use case can be extracted and explained Selected for Use Case The issue is relevant for the work and should move to an use case labels Nov 28, 2024
@github-actions github-actions bot added the needs-triage Automatically added to new issues. TF should triage them with proper labels label Nov 28, 2024
@chachamimm
Copy link

chachamimm commented Nov 28, 2024

I think it is important for the Use Cases. I think we should clarify the typical process of sleepy devices.

@egekorkan egekorkan added Needs discussion more discussion is needed before getting to a solution and removed needs-triage Automatically added to new issues. TF should triage them with proper labels labels Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Has Use Case Potential The use case can be extracted and explained Needs discussion more discussion is needed before getting to a solution Selected for Use Case The issue is relevant for the work and should move to an use case
Projects
None yet
Development

No branches or pull requests

2 participants