You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the lack of async servlet on our application server, coupled with the sudden influx of 16k clients, we need a simple http pooling to avoid an explosion of threads on our servers. We're currently using http long-polling.
The servers will be upgraded at the end of next year and we should be able to use Websockets at the same time.
In the meantime though, we're stuck with a suboptimal solution of simple http pooling.
Did I miss something ? Would it be possible to develop a simple implementation of simple http pooling on our end or would that be a daunting task ?
Thanks for your help.
The text was updated successfully, but these errors were encountered:
Hi,
From my understanding of the Atmosphere Specification, simple http pooling should be available :
https://github.com/Atmosphere/wasync/wiki/Atmosphere-Client-Specification-1.0#transports-supported
I can't find anywhere.
Due to the lack of async servlet on our application server, coupled with the sudden influx of 16k clients, we need a simple http pooling to avoid an explosion of threads on our servers. We're currently using http long-polling.
The servers will be upgraded at the end of next year and we should be able to use Websockets at the same time.
In the meantime though, we're stuck with a suboptimal solution of simple http pooling.
Did I miss something ? Would it be possible to develop a simple implementation of simple http pooling on our end or would that be a daunting task ?
Thanks for your help.
The text was updated successfully, but these errors were encountered: