The node.js http module has had support for request.connection for ages (since version 0.3.0), it's just been poorly documented. Up until the 8.x series it was tucked away in the comment of the 'connection' event. Since then, it's had its own documentation. I'd like to propose we add support for connection, but it will require some work for the Socket it returns.
My guess (and what I mentioned on slack) is that we'll want a purescript-node/purescript-node-net package, where we have Socket and all its facilities defined. If that's the case, I'm more than happy to do the work if someone can make the repo. Then, we can expose connection :: Node.HTTP.Request -> Node.Net.Socket. Does that sound about right?
The node.js
httpmodule has had support forrequest.connectionfor ages (since version 0.3.0), it's just been poorly documented. Up until the 8.x series it was tucked away in the comment of the'connection'event. Since then, it's had its own documentation. I'd like to propose we add support forconnection, but it will require some work for theSocketit returns.My guess (and what I mentioned on slack) is that we'll want a
purescript-node/purescript-node-netpackage, where we haveSocketand all its facilities defined. If that's the case, I'm more than happy to do the work if someone can make the repo. Then, we can exposeconnection :: Node.HTTP.Request -> Node.Net.Socket. Does that sound about right?