sorted by: recent | see :
popular
Content Tagged with jetty + performance
InfoQ: Comet: Sub-Second Latency with 10K+ Concurrent Users
Also known as Reverse AJAX, Comet's main goal is to allow real-time updates on the client of state changes occurring on the server by leveraging the persistent connection feature of HTTP 1.1. As described in the past on Infoq.com, along with Comet, there
Ajax
Programming
JavaScript
performance
jetty
architecture
COMET
InfoQ: Comet: Sub-Second Latency with 10K+ Concurrent Users
Sub-second latency was achievable even for 20,000 users. A tradeoff exists between latency and throughput. With 5,000 users the latency of 100ms at 2,000 messages/sec. increases to over 250ms at a throughput of 3,000 messages/sec.
Why we switched to Jetty
One of the most important traits of Web 2.0 applications is low user-perceived latency in UI update, which usually requires low latency event notification from server to client. However due to the limitations of the HTTP protocol, a server cannot initiate
Comet Daily " Blog Archive " 20,000 Reasons Why Comet Scales
aunque no sea exactamente lo que busco tiene un par de params de optimizacion jetty
Page 1 | Next >>