Skip to content
This repository has been archived by the owner on Oct 2, 2019. It is now read-only.

Making the API independent of DOM? #62

Open
ClaesNilsson opened this issue Mar 3, 2014 · 3 comments
Open

Making the API independent of DOM? #62

ClaesNilsson opened this issue Mar 3, 2014 · 3 comments

Comments

@ClaesNilsson
Copy link
Contributor

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.

@marcoscaceres
Copy link
Contributor

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.

@domenic
Copy link
Contributor

domenic commented Jun 17, 2014

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.

@ClaesNilsson
Copy link
Contributor Author

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants