• Thumbs up

  Greatest thing since sliced bread!

  posted by Joe Croft 34 days ago

  If you'd like to rate this review, please log in.
• Thumbs down

  gayyyyy

  posted by anonymous 10 days ago

  If you'd like to rate this review, please log in.
• Thumbs down

  diz shit dumd as hell shawty

  posted by anonymous 20 days ago

  If you'd like to rate this review, please log in.

View all reviews

• Forum thread added

  anirban73 created the socket proxy for windows forum thread

  posted by anirban73 1737 days ago

• Tracker artifact added

  Anonymous created the TCP_NODELAY for v2.2.4 artifact

  posted by nobody 1873 days ago

• Tracker comment added

  sparlin commented on the filter file parsing and flow control artifact

  posted by sparlin 2010 days ago

• Tracker artifact added

  nnkstone created the filter file parsing and flow control artifact

  posted by nnkstone 2272 days ago

• Forum comment added

  sday commented on the RE: Welcome to Open Discussion forum thread

  posted by sday 3147 days ago

• proxy 2.2.4 file released: proxy-2.2.4.tar.gz

  posted 3464 days ago

• File released: /proxy/2.2.4/proxy-2.2.4.tar.gz

  posted 3464 days ago

• Code committed

  sparlin committed patchset 7 of module proxy to the Proxy CVS repository, changing 2 files

  posted by sparlin 3465 days ago

• Code committed

  sparlin committed patchset 6 of module proxy to the Proxy CVS repository, changing 4 files

  posted by sparlin 3465 days ago

• proxy 2.2.3 file released: proxy-2.2.3.tar.gz

  + Fixed one more memory bug which was causing the server to die if a bunch of connections were made to it right in a row. + Got rid of threads! Some may wonder why I did this, the answer is simple. Linux threads have a limit to the amount of threads that can be opened. Please note that this is not a limit on the number of threads that can be opened at one time, but an overall limit. This is EXTREMELY bad, especially when you have a network server that (over time) will spawn thousands and thousands of threads. The answer is to use a thread pool with a fixed number of threads and a queue of connections to process. This is a cumbersome task, and not worth the hastle. So, proxy is now a forking server. + I have written a small Perl app that can be used to stress test proxy. Basically, you call it like so: ./proxy -s <port> -d 80 -D some.web.server -n ./regress server port # where server is the server running proxy, port is the port proxy is listening on, and # is the number of connections you want to make to proxy.

  posted 3466 days ago