On Wed, Jan 12, 2005 at 09:42:46AM +0100, Ortwin Gl?ck wrote: > I read it through. See my suggested changes attached. > > > Content wise: > > "This kind of use pattern is strongly discouraged because of the > excessive and unnecessary garbage collection involved." > > Is this really the problem? I mean GC performance for short-lived > objects is very good. I would rather point out that different HttpClient > instances will all have a separate connection pool which makes things > very inefficient. A shared connection pool can boost performance instead. >
Odi, Mike Even though the garbage collection in modern JVMs has improved dramatically and these days can possibly be considered neglegble, there's still a very real problem with garbage collection of open sockets. In some cases this can cause a substantial resource leak. I believe this is exactly the problem Jeanremi has been having http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=9728 This said, I see no problem in rephrasing this particular section of the guide. cheers, Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
