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

A client socket stays in connecting state if an invalid URI is given #5

Closed
flowersinthesand opened this issue May 26, 2015 · 0 comments
Closed
Assignees
Milestone

Comments

@flowersinthesand
Copy link
Member

@flowersinthesand flowersinthesand commented May 26, 2015

If an invalid URI is given that means if no transport factory specified can handle the given URI, a client socket stays in connecting state forever.

var socket = cettia.open("http://localhost:8080?transport=unknown");
socket.on("close", function() {
    console.log("never called");
});

It should try a connection with a next URI or fire error and close event if there is no remaining URI.

@flowersinthesand flowersinthesand added this to the 1.0.0-Alpha2 milestone May 26, 2015
@flowersinthesand flowersinthesand self-assigned this Feb 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.