kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/www/ruby-net-http-persistent/PLIST

15 lines
524 B
Text
Raw Normal View History

Update www/ruby-net-http-persistent package to 2.3.2. === 2.3.2 * Bug fix * Finish connections that were closed by Net::HTTP so they can be restarted. === 2.3.1 / 2011-10-26 * Bug fix * If a request object already contains a Connection header it will no longer be overridden. This allows keep-alive connections to be disabled on a per-request basis. === 2.3 / 2011-10-25 * Minor Enhancement * The time since last use for a connection is now recorded in error messages for the connection. === 2.2 / 2011-10-24 * Minor Enhancements * Added timeouts for idle connections which are set through #idle_timeout. The default timeout is 5 seconds. Reducing the idle timeout is preferred over setting #retry_change_requests to true if you wish to avoid the "too many connection resets" error when POSTing data. * Documented tunables and settings in one place in Net::HTTP::Persistent === 2.1 / 2011-09-19 * Minor Enhancement * For HTTPS connections, SSL sessions are now reused avoiding the extra round trips and computations of extra SSL handshakes. If you have problems with SSL session reuse it can be disabled by Net::HTTP::Persistent#reuse_ssl_sessions * Bug Fixes * The default certificate store is now used even if #verify_mode was not set. Issue #7, Pull Request #8 by Matthew M. Boedicker
2011-12-16 14:29:08 +01:00
@comment $NetBSD: PLIST,v 1.2 2011/12/16 13:29:08 taca Exp $
Imporging www/ruby-net-http-persistent package version 1.8.1. Manages persistent connections using Net::HTTP plus a speed fix for 1.8. It's thread-safe too! Using persistent HTTP connections can dramatically increase the speed of HTTP. Creating a new HTTP connection for every request involves an extra TCP round-trip and causes TCP congestion avoidance negotiation to start over. Net::HTTP supports persistent connections with some API methods but does not handle reconnection gracefully. net-http-persistent supports reconnection according to RFC 2616.
2011-08-12 19:29:56 +02:00
${GEM_HOME}/cache/${GEM_NAME}.gem
${GEM_LIBDIR}/.autotest
${GEM_LIBDIR}/.gemtest
${GEM_LIBDIR}/History.txt
${GEM_LIBDIR}/Manifest.txt
Update www/ruby-net-http-persistent package to 2.3.2. === 2.3.2 * Bug fix * Finish connections that were closed by Net::HTTP so they can be restarted. === 2.3.1 / 2011-10-26 * Bug fix * If a request object already contains a Connection header it will no longer be overridden. This allows keep-alive connections to be disabled on a per-request basis. === 2.3 / 2011-10-25 * Minor Enhancement * The time since last use for a connection is now recorded in error messages for the connection. === 2.2 / 2011-10-24 * Minor Enhancements * Added timeouts for idle connections which are set through #idle_timeout. The default timeout is 5 seconds. Reducing the idle timeout is preferred over setting #retry_change_requests to true if you wish to avoid the "too many connection resets" error when POSTing data. * Documented tunables and settings in one place in Net::HTTP::Persistent === 2.1 / 2011-09-19 * Minor Enhancement * For HTTPS connections, SSL sessions are now reused avoiding the extra round trips and computations of extra SSL handshakes. If you have problems with SSL session reuse it can be disabled by Net::HTTP::Persistent#reuse_ssl_sessions * Bug Fixes * The default certificate store is now used even if #verify_mode was not set. Issue #7, Pull Request #8 by Matthew M. Boedicker
2011-12-16 14:29:08 +01:00
${GEM_LIBDIR}/README.rdoc
Imporging www/ruby-net-http-persistent package version 1.8.1. Manages persistent connections using Net::HTTP plus a speed fix for 1.8. It's thread-safe too! Using persistent HTTP connections can dramatically increase the speed of HTTP. Creating a new HTTP connection for every request involves an extra TCP round-trip and causes TCP congestion avoidance negotiation to start over. Net::HTTP supports persistent connections with some API methods but does not handle reconnection gracefully. net-http-persistent supports reconnection according to RFC 2616.
2011-08-12 19:29:56 +02:00
${GEM_LIBDIR}/Rakefile
${GEM_LIBDIR}/lib/net/http/faster.rb
${GEM_LIBDIR}/lib/net/http/persistent.rb
Update www/ruby-net-http-persistent package to 2.3.2. === 2.3.2 * Bug fix * Finish connections that were closed by Net::HTTP so they can be restarted. === 2.3.1 / 2011-10-26 * Bug fix * If a request object already contains a Connection header it will no longer be overridden. This allows keep-alive connections to be disabled on a per-request basis. === 2.3 / 2011-10-25 * Minor Enhancement * The time since last use for a connection is now recorded in error messages for the connection. === 2.2 / 2011-10-24 * Minor Enhancements * Added timeouts for idle connections which are set through #idle_timeout. The default timeout is 5 seconds. Reducing the idle timeout is preferred over setting #retry_change_requests to true if you wish to avoid the "too many connection resets" error when POSTing data. * Documented tunables and settings in one place in Net::HTTP::Persistent === 2.1 / 2011-09-19 * Minor Enhancement * For HTTPS connections, SSL sessions are now reused avoiding the extra round trips and computations of extra SSL handshakes. If you have problems with SSL session reuse it can be disabled by Net::HTTP::Persistent#reuse_ssl_sessions * Bug Fixes * The default certificate store is now used even if #verify_mode was not set. Issue #7, Pull Request #8 by Matthew M. Boedicker
2011-12-16 14:29:08 +01:00
${GEM_LIBDIR}/lib/net/http/persistent/ssl_reuse.rb
Imporging www/ruby-net-http-persistent package version 1.8.1. Manages persistent connections using Net::HTTP plus a speed fix for 1.8. It's thread-safe too! Using persistent HTTP connections can dramatically increase the speed of HTTP. Creating a new HTTP connection for every request involves an extra TCP round-trip and causes TCP congestion avoidance negotiation to start over. Net::HTTP supports persistent connections with some API methods but does not handle reconnection gracefully. net-http-persistent supports reconnection according to RFC 2616.
2011-08-12 19:29:56 +02:00
${GEM_LIBDIR}/test/test_net_http_persistent.rb
Update www/ruby-net-http-persistent package to 2.3.2. === 2.3.2 * Bug fix * Finish connections that were closed by Net::HTTP so they can be restarted. === 2.3.1 / 2011-10-26 * Bug fix * If a request object already contains a Connection header it will no longer be overridden. This allows keep-alive connections to be disabled on a per-request basis. === 2.3 / 2011-10-25 * Minor Enhancement * The time since last use for a connection is now recorded in error messages for the connection. === 2.2 / 2011-10-24 * Minor Enhancements * Added timeouts for idle connections which are set through #idle_timeout. The default timeout is 5 seconds. Reducing the idle timeout is preferred over setting #retry_change_requests to true if you wish to avoid the "too many connection resets" error when POSTing data. * Documented tunables and settings in one place in Net::HTTP::Persistent === 2.1 / 2011-09-19 * Minor Enhancement * For HTTPS connections, SSL sessions are now reused avoiding the extra round trips and computations of extra SSL handshakes. If you have problems with SSL session reuse it can be disabled by Net::HTTP::Persistent#reuse_ssl_sessions * Bug Fixes * The default certificate store is now used even if #verify_mode was not set. Issue #7, Pull Request #8 by Matthew M. Boedicker
2011-12-16 14:29:08 +01:00
${GEM_LIBDIR}/test/test_net_http_persistent_ssl_reuse.rb
Imporging www/ruby-net-http-persistent package version 1.8.1. Manages persistent connections using Net::HTTP plus a speed fix for 1.8. It's thread-safe too! Using persistent HTTP connections can dramatically increase the speed of HTTP. Creating a new HTTP connection for every request involves an extra TCP round-trip and causes TCP congestion avoidance negotiation to start over. Net::HTTP supports persistent connections with some API methods but does not handle reconnection gracefully. net-http-persistent supports reconnection according to RFC 2616.
2011-08-12 19:29:56 +02:00
${GEM_HOME}/specifications/${GEM_NAME}.gemspec
Reference in a new issue Copy permalink