Skip to content

Automatically exhaust response entities returned by ClientResource #968

Open

Description

@jlouvel

Currently if the response entity isn't consumed or if exhaust() isn't called explicitly, the connection is blocked.

The idea is to have a default setting that would automatically exhaust() the entity upon release() of the ClientResource. Note that today we only keep track of the latest response, not the history of all calls.

Reported by @stoffeg

Activity

  1. jlouvel commented on Oct 24, 2014

    @jlouvel
    CollaboratorAuthor
  2. added this to the 2.3 M4 milestone on Oct 24, 2014
  3. modified the milestones: 2.3 M4, 2.3 RC1 on Nov 2, 2014
  4. modified the milestones: 2.3 RC1, , 3.0 M1 on Nov 22, 2014
  5. modified the milestones: 3.0 M1, on Jan 20, 2015
  6. modified the milestones: , Unplanned on May 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions