Skip to content

hyper-util: What is the roadmap for the legacy client? #3891

Open
@NielDuysters

Description

@NielDuysters

Hi

I am volunteering for the Tor Project which is making a new implementation in Rust called Arti.

Previously we had a crate providing an extra layer on hyper allowing it to be easily implemented into Arti. But since hyper 1.x this crate was deprecated because making a request through Arti using hyper became easier as this example demonstrates.

But we noticed that the lack of a custom connector is now missed by our users. In MR!2941 we are planning on resurrecting the arti-hyper crate.

But AFAIK this is only a logic choice when the user is able to use the legacy client for hyper_util to use the request method from that client to make requests.

I am wondering what the planned roadmap for the legacy client in hyper_util actually is. In client/legacy/client.rs I e.g see the following comment:

//! The legacy HTTP Client from 0.14.x
//!
//! This `Client` will eventually be deconstructed into more composable parts.
//! For now, to enable people to use hyper 1.0 quicker, this `Client` exists
//! in much the same way it did in hyper 0.14.

What exactly is meant by this? Are you planning on supporting this legacy client in the far future too?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions