search

httpslocal / usecases

discussion about use cases
Other
17 stars 11 forks source link

[Use cases] Add a use case for normal access pattern. #28

Closed dajiaji closed 5 years ago

dajiaji commented 5 years ago

Thanks @tomoyukilabs for drafting the CG report.

As I mentioned in my proposal, I think we can categorize two device access patterns principle for local HTTPS as follows.

  • Normal access pattern: the device has web contents and a user types the address of the device (e.g., ‘https://device.local’) on the browser directly and receives the contents.
  • Cross-origin access pattern: the device has API endpoints and a web frontend loaded on a browser from the internet (hereafter, simply called ‘web service’) accesses the APIs with a browser API (e.g., fetch API) and receives the contents.

Although The current CG report draft includes many use cases for the cross-origin access pattern, there is no use case for the normal access pattern. So I'd like to add a use case for the normal access pattern by modifying UC-07. It is because the UC-07 treats home gateways which can be accessed by way of the normal access pattern and, in addition, I don't want to increase the number of use cases any more.

Could you check the PR?

daniel-kun commented 5 years ago

@dajiaji Good find! Apparently I didn't read the use case good enough, because I thought it would explicitly address the local, direct HTTPS access via browser. But apparently it didn't, so thanks for this clarification. This is the most important use-case for the numerous Home Automation gateways that offer a Web Frontend for configuration and use.

dajiaji commented 5 years ago

Hmm, I couldn't notice your mentions and reviews till now...

dajiaji commented 5 years ago

@daniel-kun Thanks for your comments! @tomoyukilabs Thanks. I revised UC-07 according to your comments.

tomoyukilabs commented 5 years ago

@dajiaji LGTM. I've merged the PR. I'll generate index.html with Bikeshed later. Thanks!