Re: [jetty-users] (Am I) using persistent connections with Jetty
If you use HTTP1.1 from the clients the connections will be persistent
by default. Even if the client does not close them, after some idle
timeout jetty can close them (see
of maxIdleTime and lowResourcesMaxIdleTime).
> Would using Jetty (7? 8?) and persistent connections make sense in situations where clients more or less constantly stream data to the server?
> For example, imagine a system where client applications:
> * are running on hundreds of nodes of some cluster
> * are constantly collecting performance metrics
> * are sending these metrics via HTTP to some server
> * Would it make more sense to have clients keep persistent connections with the server instead of opening/closing them?
> * If I'm not explicitly closing HTTP connections on either client (using HttpClient lib) or server (servlet running in Jetty 7.*) side, am I effectively already keeping all connections open/persistent?
> Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm >
> jetty-users mailing list
> [hidden email] > https://dev.eclipse.org/mailman/listinfo/jetty-users