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

Socket.io timeouts? #42

Closed
JoshZA opened this issue Apr 27, 2016 · 2 comments · Fixed by feathersjs-ecosystem/transport-commons#15
Closed

Socket.io timeouts? #42

JoshZA opened this issue Apr 27, 2016 · 2 comments · Fixed by feathersjs-ecosystem/transport-commons#15

Comments

@JoshZA
Copy link

JoshZA commented Apr 27, 2016

app.authenticate({
    type: 'local',
    'email': 'admin@feathersjs.com',
    'password': 'admin'
}).then(function(result){
    console.log('Authenticated!', app.get('token'));
}).catch(function(error){
    console.error('Error authenticating!', error);
});

Win 10 with node v5.10.0

SocketIo only, no rest plugin loaded

When I run this, and there's no feathers server running - the Catch handler never fires, code just runs infinitely

Surely, there should be some default timeout for this?

@daffl
Copy link
Member

daffl commented Apr 28, 2016

Related: feathersjs-ecosystem/transport-commons#9.

@daffl
Copy link
Member

daffl commented Apr 28, 2016

Socket client timeouts are now implemented and set to 5000ms by default. They can be configured with app.configure(socketio(socket, { timeout: 2000 })) (see the documentation)

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

Successfully merging a pull request may close this issue.

2 participants