0

i have a website that displays all kind of info to the client. It has a chat, a different kind of chat, a couple of notifications, etc.

The way i build this is that every ajax call, for each of the chat and notification, happens every second. So at any given point i have at lease 5 requests happening.

for example the chat has to look alive, if there is a email notification i want to show it when it happens, if there is a friend request i want to show it right then.

Everything looks ok so far, but i am wondering is there is a limit or if is just bad to do it like this. In the same time i want the user experience t be the best.

Any ideas?

Patrioticcow
  • 26,422
  • 75
  • 217
  • 337
  • 1
    The limit really applies to your server, not so much to the client. And the answer to that is "however many it's designed to handle". – Blazemonger May 09 '12 at 21:23
  • 1
    If you want the user experience to be "the best", you should look into [long-polling](http://en.wikipedia.org/wiki/Push_technology). – user229044 May 09 '12 at 21:28

1 Answers1

1

It does, if you really make concurrent calls and if the concurrency really matters to you!

Limited number of concurrent requests are allowed per domain in any browser, you can read more here, if you overuse it, there is the possibility your requests will be blocked waiting for others to complete! However if it doesn't concern you the browser will make the queue of requests and send it to the server whenever it is free.

Community
  • 1
  • 1
Kamyar Nazeri
  • 25,786
  • 15
  • 50
  • 87