From: Richard Zidlicky Date: 2003-07-18T07:11:09+09:00 Subject: Re: OO Design question for Net::HTTP caching extension On Thu, Jul 17, 2003 at 02:41:55PM +0900, Aredridel wrote: > > > One architectural suggestion: rather than extending/overriding Net::HTTP, > > make your cache a separate object. > > On second thought, integrating as tightly as I'd like with Net::HTTP, > while it works, isn't practical because the cache can't be checked > easily until after the socket's opened. > > I'll probably go with a delegator much like Net::HTTP::Proxy. We'll > see. This is useful code, and it's already nearly good enough for my > uses but deserves some full development because I can see a lot of need. actually I found it quite irritating that proxy isn�t intergated more transparently into Net::HTTP (not to mention complete lack of support for ftp proxy) Every Perl or Python tool will use http_proxy and no_proxy environment variables by default and I see no reason Ruby tools should do differently. Richard