On Jan 6, 3:04 pm, Marnen Laibow-Koser <[email protected]> wrote: > Please quote when replying. > > Tony Primerano wrote in post #972913: > > > It looks like HTTParty uses Net::HTTP so I'll just stick with that. > > Stick with *which*? > I'll just call Net::HTTP directly. I have a simple GET request that returns some simple CSV data.
> > > > I got burned by so many deprecated gems moving from Rails 2 to Rails 3 > > that use them sparingly now. :-\ > > I see this attitude a lot, and I believe it is silly. If there's > already a library out there that makes your life easier, don't reinvent > the wheel. Laziness is one of the cardinal virtues for programmers! I'm not really reinventing the wheel here. HTTParty is fine but I just wanted a connection timeout via Net::HTTP, which I learned how to do by looking at HTTParty code. If a 1000 line gem is saving me 10 lines of code I'm better off not using it. Gems like authlogic are essential. If I needed more HTTParty features I would use it but for now the standard library is just fine. :-) > > Best, > -- > Marnen Laibow-Koserhttp://www.marnen.org > [email protected] > > -- > Posted viahttp://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
