Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'connect-timeout' is possibly misleading #19

Closed
kevinburkeshyp opened this issue Aug 3, 2015 · 2 comments
Closed

'connect-timeout' is possibly misleading #19

kevinburkeshyp opened this issue Aug 3, 2015 · 2 comments
Assignees
Labels

Comments

@kevinburkeshyp
Copy link

I would expect a library named connect-timeout to enable the ability to time out a socket CONNECT request - something I believe that the node request library does not currently offer, for example. I was surprised to learn it had more to do with timing out app requests.

@dougwilson
Copy link
Contributor

This module comes from a long time ago, where everything connect-* was for the connect web framework. Changing a module's name is not trivial and of course all it will do is make two modules on npm: connect-timeout and whatever the new name is. Npm does not offer the ability to rename modules.

@dougwilson dougwilson self-assigned this Aug 3, 2015
@kevinburkeshyp
Copy link
Author

Fair enough! Yeah I don't know what would be better besides just merging support into the places that should have it

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

No branches or pull requests

2 participants