You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2019. It is now read-only.
As desirable as this is, it's not usually possible to do this because of the reliance on WebIDL. I would not put a very strong focus on this right now.
I don't think it's that hard. WebIDL semantics are just JS semantics. Indeed all you would need to do is use JS error types instead of DOMException. (DOMError should not be used any more.) DOMString is just WebIDL's funny way of saying JS string.
Ok, thanks for your inputs on this Marcos and Domenic. I'll look into it when I resume my work on this API.
Just for your information: I have had to focus on a lot of other tasks the latest month so no updates to this API has been done for a while. However, I plan to start working on it in August. The two main tasks are algning with the latest version of the Streams API and rewriting of the TCPServer interface to be based on Streams in a way similar to what I have done for TCPClient and UDP.
Consider making the API indepedent of DOM so it could be used by JS server implementations, web workers etc.
That would mean that refs to DOMError, DOMExeptions and DOMString need to be replaced.
The text was updated successfully, but these errors were encountered: