Skip to content

Merge HttpClient component into this component #148

Description

@clue

Here's the current situation:

  • This Http component: Event-driven, streaming plaintext HTTP and secure HTTPS server for ReactPHP.
  • HttpClient component: Asynchronous HTTP client library.

This is not exactly ideal, they share quite a bit of common code.

Also, I believe this situation may be a bit confusing for consumers of this package. In particular our Datagram component provides both client and server side for datagram sockets (UDP).

As such, I'd vote for merging these two components into a single Http component.

Activity

  1. added this to the milestone on Nov 28, 2017
  2. cebe commented on Jan 15, 2018

    @cebe

    they share quite a bit of common code.

    Could you point out which code they share? When looking at the code I could not find anything obvious.

  3. clue commented on Jan 16, 2018

    @clue
    MemberAuthor

    Could you point out which code they share? When looking at the code I could not find anything obvious.

    Good point. You're right in that they currently don't share much code (except for chunked transfer encoding maybe). However, they share quite a bit of domain knowledge. In particular, we've had to backport fixes / minor features from this component to the http-client repeatedly.

    Also, looking at its roadmap (reactphp/http-client#79) reveals that we plan to implement PSR-7 interfaces (reactphp/http-client#41) also for the http-client. Once this is in, they will share significantly more code.

  4. modified the milestones: , v1.0.0 on Jun 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions