draggett / arena-webhub Goto Github PK

The aim is to simplify the API used by client developers still further by using getters and setters for synchronous updates to object properties, and by treating actions as object methods that return promises. The client platform should validate data and thrown an exception if the app tries to pass a value that is invalid in respect to the thing description. Asynchronous errors are reported via events, e.g. loss of connection or an error reported by the server, but note that actions are asynchronous and the app should deal with errors through the promise returned when invoking an action. We need to agree on a means to separate the system events from the events declared in thing descriptions. One idea is by event name, but another idea would be to an API for subscribing to system events, e.g. to set onerror handlers. The error pattern is common place for node and for the browser DOM.

The client library needs to handle the visibility state API in order to re-open Web Socket connections that were closed when a tab has been hidden for some time. The following probably is also true for Server-Sent events - that needs testing. The client library in "wot.js" could listen for "visibilitychange" event on the document to determine when to test if the socket has closed and re-open it. Code that sends to a web socket should likewise test for a closed socket and reopen it - note that this will mean deferring a send until the socket opens.

I need to work on the account management example to demonstrate how to support account registration, second factor authentication, JWT processing, etc.

I need to implement and test the remote access API as described in the README