The future of httpi

[pcai]

This gem has been downloaded 57 millions times - so lots of people obviously found it very useful, which is great! But a lot has changed in the ~12 years since httpi was first released.

For one, faraday has grown over time to, as far as I can tell, encapsulate a superset of httpi's functionality. Because of the larger community backing faraday's active development, and an aging backlog of features on httpi's roadmap (that essentially duplicate functionality available in faraday and other gems), I propose:

1. switching httpi to maintenance mode; no new features (existing work-in-progress to be evaluated on a case by case basis)
2. increasing emphasis on httpi documentation, especially on migration paths to faraday, and especially for those who need its features which are missing in httpi
3. investigating migrations in related projects (e.g., savon) away from httpi

This will help the community focus its efforts and avoid duplicating work. As will be apparent to most observers, there is precious little attention to go around, and maintenance of savon projects in general would go smoother with a smaller surface area to focus on.

I am looking for additional feedback and suggestions on the path forward. Then I plan to resolve the lingering issues/PRs and ambiguity in this repo accordingly. Thanks to all past (and future) httpi contributors in advance

[olleolleolle]

Cc @iMacTia

[iMacTia]

The Faraday team would be happy to collaborate with the httpi team on defining a roadmap to add the missing functionality and make the migration as smooth as possible ❤️

Let me know if interested and we can sync via Discussions or Slack 👍

[rogerleite]

Hi @pcai!

As a past HTTPI contributor, I agree to switch it to maintenance mode.

I am looking for additional feedback and suggestions on the path forward.

The emphasis on documentation and migration paths to faraday seems good. The only feature that comes to my mind is NTLM support that I don't know if Faraday supports it.

The site http://httpirb.com/ is a problem too. @rubiii owns the dns and I don't have access to it.

[pcai]

Thanks everyone for your input and your support!

@rogerleite I only skimmed this, but it seems to document a workaround with faraday + net_http_persistent + ntlm gems?

@rubiii I will send you an email to coordinate DNS (lets move to gh pages like with https://www.savonrb.com and we'll not have to worry about hosting)