有什么好例子吗? 它应该适用于移动和普通浏览器。I have created a small and simple chat with signalr on a azure website. That doesn't work as expected.After some hours on Google I found out, that signalr should be implemented different on Azure.What is best practise?Any good examples?It should work on both mobile and in normal browsers.推荐答案 此链接和说明解决了我在Signalr和Websockets上的问题在Azure上 我发现了这个: http://www.asp.net/signalr/overview/deployment/using-signalr-with-azure-web-sites#websocket 这个: https://azure.microsoft.com/en-us/blog/introduction-to-websockets-on-windows-azure-web-sites/ 请注意这一部分: WebSockets连接限制 目前Azure网站已实现对并发WebSockets连接数量的限制支持每个运行的网站实例。每个缩放模式的每个网站实例支持的WebSockets连接数如下所示: 免费:(5)每个网站实例的并发连接 共享:(35)每个网站实例的并发连接 基本:(350)每个网站实例的并发连接 标准:无限制 如果您的应用程序尝试打开比允许限制更多的WebSocket连接,Windows Azure网站将返回503 HTTP错误状态代码。 注意:术语网站实例表示以下内容 - 如果您的网站缩放为在(2)个实例上运行,则计为(2)运行网站实例。This links and notes solved my issues on Signalr and Websockets on AzureI found this:http://www.asp.net/signalr/overview/deployment/using-signalr-with-azure-web-sites#websocketAnd this:https://azure.microsoft.com/en-us/blog/introduction-to-websockets-on-windows-azure-web-sites/Note this part:WebSockets Connection LimitsCurrently Azure Web Sites has implemented throttles on the number of concurrent WebSockets connections supported per running website instance. The number of supported WebSockets connections per website instance for each scale mode is shown below:Free: (5) concurrent connections per website instanceShared: (35) concurrent connections per website instanceBasic: (350) concurrent connections per website instanceStandard: no limitIf your application attempts to open more WebSocket connections than the allowable limit, Windows Azure Web Sites will return a 503 HTTP error status code.Note: the terminology "website instance" means the following - if your website is scaled to run on (2) instances, that counts as (2) running website instances. 这篇关于SignalR在天蓝色的聊天的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持! 上岸,阿里云!
08-04 06:15
查看更多