axum is an ergonomic and modular web framework built with Tokio, Tower, and Hyper

  • Ephera
    link
    fedilink
    English
    arrow-up
    6
    ·
    8 days ago

    We got done upgrading to 0.7 at $DAYJOB just a few weeks ago. 🫠

    But this release does look significantly more manageable. 0.7 was the release where they switched to http 1.0 and hyper 1.0, which meant we had to upgrade the entire networking stack in one fell swoop. And it’s a distributed application, so there’s a lot of components that do networking…

      • Ephera
        link
        fedilink
        English
        arrow-up
        2
        ·
        8 days ago

        Yeah, it was kind of the last real blocker, but we have a somewhat special setup where we serve HTTP and gRPC on the same port, for which we had integrated Axum with Tonic. Before the 0.7 release, Axum had an example for how to do this. After the release, that example was commented out with a TODO. So, we were kind of waiting for that to be documented. I mean, I didn’t have terribly high hopes, as they probably wouldn’t put a TODO in there, if it was trivial to upgrade, but if they struggled with it, I really didn’t want to have to figure it out myself.

        But they seem to have actually even removed the example now, so I guess, it was the right call to just push through and throw down whatever ugly code makes it work…

        • jplatte@discuss.tchncs.deOP
          link
          fedilink
          arrow-up
          3
          ·
          8 days ago

          Ah yeah, we recently removed that example because it was kind of hard to upgrade in a nice way. One could likely take the example from the PR branch here and submit it to tonic instead. I think they might have a bigger interest in having it.