From Atmosphere mailing lists:
> Hi folks,
> I have just found that jquery plugin uses maxRequest 60 by default.
> According to  maxRequest is 'The maximum number of requests that will be executed. Once the maximum gets reached, the connection will be closed.'
> However it makes sense only for long-polling transport, because the connection is closed each time when client pushes/recieves the message. But i am not sure how it affects the streaming transport.
> I can send as many messages as i want with streaming transport. I suppose only connection interrupt (or timeout and maxStreamingLength ?) between client and server may force reconnect, so the counter will be increased. So after some amount of time the jquery plugin may silently stop to work and you will not find the reason easily if you don't know about the default value of this parameter . So behavior of this parameter in streaming transport is not consistent with pooling transport.
> Why max requests are limited by default? Does it make any sense?
Because of proxy that close connection (with all transports), we need to stop sending requests after some time ... if the server goes down or anything related, the browser will keep trying, so that's why I've added this property. Does it make sence?