Skip to content

Should we expose a sync version of fetch_ohttp_keys? #1489

Open

Description

@benalleng

Following some review in the liana implementation it was brought to my attention it might be useful to make a sync version of fetch_ohttp_keys() publicly available so we don't have to manually re-implement it where async would be a burden.

Activity

  1. DanGould commented on Apr 21, 2026

    @DanGould
    Member

    wait didn't @spacebear21 just say that this is a very unlikely scenario? Is your link to Liana a counterpoint to his claim which I can't find right now

  2. spacebear21 commented on Apr 21, 2026

    @spacebear21
    Collaborator

    My claim was regarding implementations that use FFI language bindings fwiw

  3. DanGould commented on Apr 22, 2026

    @DanGould
    Member

    I feel like Liana is the type of implementation where they'd want to roll their own fetch_ohttp_keys unless they coincidentally also used the same HTTP client. Definitely a place bitreq makes more sense than reqwest, but if we're supporting bitreq then it makes sense for liana to use io and perhaps for us to expose that functionality for them.

  4. xstoicunicornx commented on Apr 26, 2026

    @xstoicunicornx
    Collaborator

    FWIW I was the one who made the Liana review and I had not realized at the time that fetch_ohttp_keys was async. So I think probably appropriate to close this issue until there is at the very least one other implementation that would use this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions