11
edits
WebAPI/WebSerial: Difference between revisions
no edit summary
(added security section) |
No edit summary |
||
| Line 7: | Line 7: | ||
== Security Implications == | == Security Implications == | ||
One needs to consider the security implications of giving access to hardware and connected devices to websites. The solution should not be any different than the geolocation and camera APIs, as in asking the user to give access to each particular website, but it should be investigated nonetheless. | One needs to consider the security implications of giving access to hardware and connected devices to websites. The solution should not be any different than the geolocation and camera APIs, as in asking the user to give access to each particular website, but it should be investigated nonetheless. | ||
== Suggested API == | |||
Serial communication APIs are generally pretty straightforward. Chrome's API is actually quite a good reference API, and there are more provided below. Here is a draft of the suggested API. | |||
* getPorts() | |||
* open() | |||
* close() | |||
* read() | |||
* write() | |||
* flush() | |||
* getControlSignals() | |||
* setControlSignals() | |||
== Implementation == | == Implementation == | ||