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

Default eventing mechanism in HTTP #199

Open
egekorkan opened this issue Nov 9, 2022 · 3 comments
Open

Default eventing mechanism in HTTP #199

egekorkan opened this issue Nov 9, 2022 · 3 comments
Labels
http related to http protocol binding Needs discussion

Comments

@egekorkan
Copy link
Contributor

Currently, if there is an event affordance or an observable property, there has to be a subprotocol in place in order to do real eventing, e.g. sse, longpoll etc. However, we do not mandate this and I think we should. If there is no subprotocol, different implementations will do different default assumptions (see eclipse-thingweb/node-wot#863).

Two important questions for everyone:

  1. Should there be a default subprotocol in HTTP forms with eventing mechanism (events and observeproperty)? If there should be, what mechanism should it be?
  2. If there is no subprotocol field, should a validation of the TD fail? We can provide the JSON Schemas that allow this validation to be happen on top of the basic schema for TDs. Furthermore, should we restrict the values of subprotocol in the case of an HTTP form?
@egekorkan egekorkan assigned egekorkan and unassigned egekorkan Nov 9, 2022
@egekorkan egekorkan added the http related to http protocol binding label Nov 9, 2022
@egekorkan
Copy link
Contributor Author

egekorkan commented Nov 22, 2022

Sort of duplicate of #114 but I would prefer to move the discussion here since the only decision in that issue discussion was to add a possible mappings table in each protocol binding template.

@danielpeintner
Copy link
Contributor

@egekorkan do you have a use-case for proposing a default eventing mechanism in HTTP or is the rational mainly to avoid issues and increase interoperability?

@egekorkan
Copy link
Contributor Author

No this is definitely not a use case requiring discussion but more about alignment. If there is no default or mandatory subprotocol field, that form should be invalid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
http related to http protocol binding Needs discussion
Projects
None yet
Development

No branches or pull requests

2 participants