我有一个使用 SignalR 和 MVC 运行的简单聊天客户端项目,它与ASP.Net One几乎相同(我只是在试验——客户端代码是相同的)。我已经连接了以下内容以观察发生的事情:
$.connection.hub.stateChanged(function(state){console.log(state)});
连接工作正常,但我注意到如果我关闭 IIS Express 并在 Chrome 中观看控制台,我会看到:
//As you would expect the state goes from connected to connecting
Object {oldState: 1, newState: 2}
//Then it times out after about 30 secs and throws this awesomeness at the console
WebSocket connection to 'ws://localhost:61623/signalr?transport=webSockets&connectionToken=VDF640emz7PFMToC6vxle_5-7QS5dZMszV4SPbQO7EFEmSSsITnwKsZreqfl4MGq8TXitG2xB5F-2ZdHp-2t3shPzN2hemTY1ZmEWlB8NOn5orUVexaSoARk9XjEO5B00&connectionData=%5B%7B%22name%22%3A%22chathub%22%7D%5D&messageId=B%2C7%7CL%2C0%7CM%2C0%7CN%2C0&tid=0' failed: WebSocket is closed before the connection is established. jquery.signalR-1.0.1.js:1117
//Reconnecting to Disconnecting - so why the error above?
Object {oldState: 2, newState: 4}
//Then radio silence if I start IIS again...
2个问题:
尝试重新连接失败时如何避免错误?
为什么 SignalR 不继续尝试连接到 IIS?我的印象是这就是技术的重点......
编辑:同样的事情也发生在 FireFox