[Inoob]

I understand that many browsers have limitations (such as 6 requests per "group" meaning I guess how many tabs you have for lets say 'google.com')

Now, I only have 1 constant request..

It starts, and has a timeout of 60 seconds, I then start a separate request to "send" a message to the server, which will impact what is "returned" by the server on the longpoll connection..

My current model, or design, albiet fully functional, has 1 major flaw..

A request is made to the server, which islong polled, (E.G. thrown into a loop)

The Long Poll will continue to long poll until one of the following two conditions are satisfied..

1) The time() is > initial_time+60seconds
2) There is data to be displayed, and found..

the above works just fine.. However, while this is running, if I try to send a Message to the server, javascript wants to wait until the previous request has finished, before sending another request.. which sometimes could take a full minute to showup.. Hardly real time, which defeats the purpose of long polling?

I figure maybe you can't have two connections running at the same exact time in Google Chrome, so I stop the current long poll

- XMLHttpRequest.abort() -

But that still, takes until the request (the server side code) ends processing and still takes up to 60 seconds until the message is sent to the server (which seems to be because it is processing till a specific time)...

this is extremely frustrating..

is there any way to fix this problem?

Thank you all very much!