-
Notifications
You must be signed in to change notification settings - Fork 7.3k
The TLS API is inconsistent with the TCP API #1467
Comments
i like |
Well thats fine with me. I would be nice if the TLS |
And there are no callback in the TCP 'createConnection' function. It would be nice if the new |
@AndreasMadsen - In v0.5, with exports.connect = exports.createConnection = function(port /* [host], [cb] */) { |
please review. |
Nice that the 'connect' method is documented, but why have two names for the same function. Please consider to remove the documentation for 'createConnection' or just mark it deprecated. But the TLS api still need to emit a 'connect' or a 'secureConnect' event, when a connection is made. |
@AndreasMadsen - Thanks for your review. And I added 'secureConnect' event. |
The |
@AndreasMadsen - v0.4 branch was merged to the master, then I added |
I have nothing more to say. |
@ry or @bnoordhuis, can you review 0f12a91? |
Reabased. |
@koichik: LGTM |
@bnoordhuis - Thanks! |
@AndreasMadsen - Thanks for the suggestion. |
Nice to help |
Thanks! |
To create a request using TLS the
connect
method should be used, to do the same with TCP thecreateConnection
should be used. There are also noSocket
constructor in the TLS API.I would be nice if
connect
was renamed tocreateConnection
and there was aSocket
constructor in the TLS API.The text was updated successfully, but these errors were encountered: