[英]SignalR Client Default Fallback Transport
For the case of an SignalR client using .Net Framework 4.0 to connect to the server (therefore no WebSockets transport supported) which would be the next fallback transport ? 对于使用.Net Framework 4.0连接到服务器的SignalR客户端 (因此不支持WebSockets传输),这将是下一个后备传输?
Moreover, if there is a fallback chain it would be great to know it. 而且,如果有一个后备链,那么知道它会很棒。
From https://docs.microsoft.com/en-us/aspnet/signalr/overview/getting-started/introduction-to-signalr#transports-and-fallbacks the following are used if WebSockets is unavailable: 从https://docs.microsoft.com/en-us/aspnet/signalr/overview/getting-started/introduction-to-signalr#transports-and-fallbacks ,如果WebSockets不可用,则使用以下内容:
Update: The latest docs are available here: http://www.asp.net/signalr/overview/signalr-20/getting-started-with-signalr-20/introduction-to-signalr 更新:最新文档可在此处获取: http : //www.asp.net/signalr/overview/signalr-20/getting-started-with-signalr-20/introduction-to-signalr
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.