SignalR chat on azure

Question

1.00/5 (1 vote)

See more:

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.

Posted 28-Sep-15 6:36am

Member 10860651

Add a Solution

Comments

Vincent Beek 29-Sep-15 12:59pm

Can you share the link to what you found on Google please?

Member 10860651 29-Sep-15 15:55pm

I found this:
http://www.asp.net/signalr/overview/deployment/using-signalr-with-azure-web-sites#websocket
And this:
https://azure.microsoft.com/en-us/blog/introduction-to-websockets-on-windows-azure-web-sites/
Note this part:
WebSockets Connection Limits

Currently 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 instance
Shared: (35) concurrent connections per website instance
Basic: (350) concurrent connections per website instance
Standard: no limit
If 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.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Member 10860651 · Answer 1 · 2015-09-29T09:57:00

This links and notes solved my issues on Signalr and Websockets on Azure
I found this:
http://www.asp.net/signalr/overview/deployment/using-signalr-with-azure-web-sites#websocket
And this:
https://azure.microsoft.com/en-us/blog/introduction-to-websockets-on-windows-azure-web-sites/

Note this part:
WebSockets Connection Limits

Currently 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 instance
Shared: (35) concurrent connections per website instance
Basic: (350) concurrent connections per website instance
Standard: no limit
If 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.