-
Notifications
You must be signed in to change notification settings - Fork 8
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
Reference device #69
Reference device #69
Conversation
Additionally all TDs that were used during the PlugFests showed that 95% of TDs were around 8KB in size. | ||
</p> | ||
<p> | ||
A maximum size of a TD of 16 KB leaves enough headroom and can be still handled on embedded devices with 64-128KB of RAM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed in today's meeting, many WoT produces are not able to fulfill such kind of limitation. E.g., a Sentron PAC has over 50 different datapoints (s. page 99).
This 16k limit is mainly meant to address WoT consumer. But what are realistic use cases? I assume that a node that also consume TDs will always be more powerful than a WoT producer only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sebastiankb
Thanks Sebastian, this makes the discussion much more concrete.
Which size limit would you recommend for TDs produced by this device?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So far, I see no need for such a restriction in the core profile with HTTP/JSON. But maybe I'm missing something. I would recommend that in the next session we discuss what kind of (realistic) scenarios you need for this constraint. A good orientation can be this figure here.
virtual F2F on 23.6.: |
Preview | Diff