5 ms·

What do you use now? Warp?

by munmaek 7y ago

deleted 7y ago
[deleted]
dbcfd 7y ago
Right now, if you want async/await, you either have warp or tide. Hopefully gotham or rocket gets around to updating.
- rudedogg 7y ago
  Can anyone comment on how close Rocket is to a 0.5 release? I’ve been wondering for awhile, but opening an issue to ask seems annoying.
  - agersant 7y ago
    I don't have any insight but you can subscribe to this issue to see how things are moving: https://github.com/SergioBenitez/Rocket/issues/1065 https://github.com/SergioBenitez/Rocket/issues/1065
  - nicoburns 7y ago
    I've been following this quite closely. Most of the work seems to be done. But development is very stop-start in fits and bursts, so it's hard to tell how much longer it will take.
- kevinastone 7y ago
  Gotham will be async-ready once this PR lands and the next release is published: https://github.com/gotham-rs/gotham/pull/370 https://github.com/gotham-rs/gotham/pull/370
  - anon463637 7y ago
    Noice. To me, Gotham makes more sense because it depends on stable, whereas Rocket uses nightly. Anything depending on nightly seems inherently more fragile and un-future-proof (no pun intended).
_-___________-_ 7y ago
We just use hyper directly, with a small amount of glue code to use serde_json, serde_urlencoded for body parsing and a very simple (and very fast) router of our own creation. This approach also made it very simple for us to introduce std-future/async-await in a gradual way.
mojzu 7y ago
I've been in the process of switching to tonic for the last few of weeks. Based on hyper/tower and has async/await support. It's a gRPC server rather than HTTP, so I've been using it with grpc-gateway to provide an HTTP OpenAPI v2 interface. It has automated quite a few things I found dull to do in other server frameworks, from the gRPC .proto file I can generate: - Rust server request/response types and request handler stubs. - grpc-gateway files and an OpenAPI v2 json spec. - Client side typescript types and request/response handlers from the OpenAPI spec. So now the process of adding a new endpoint is much less time consuming and involves writing less repetitive and error prone code. As mentioned above I've only been using it a few weeks but so far it has been great, easier to use than actix-web and felt no less responsive.

What do you use now? Warp?

deleted 7y ago

[deleted]

dbcfd 7y ago

Right now, if you want async/await, you either have warp or tide. Hopefully gotham or rocket gets around to updating.

rudedogg 7y ago
Can anyone comment on how close Rocket is to a 0.5 release? I’ve been wondering for awhile, but opening an issue to ask seems annoying.
- agersant 7y ago
  I don't have any insight but you can subscribe to this issue to see how things are moving: https://github.com/SergioBenitez/Rocket/issues/1065 https://github.com/SergioBenitez/Rocket/issues/1065
- nicoburns 7y ago
  I've been following this quite closely. Most of the work seems to be done. But development is very stop-start in fits and bursts, so it's hard to tell how much longer it will take.
kevinastone 7y ago
Gotham will be async-ready once this PR lands and the next release is published: https://github.com/gotham-rs/gotham/pull/370 https://github.com/gotham-rs/gotham/pull/370
- anon463637 7y ago
  Noice. To me, Gotham makes more sense because it depends on stable, whereas Rocket uses nightly. Anything depending on nightly seems inherently more fragile and un-future-proof (no pun intended).

_-___________-_ 7y ago

We just use hyper directly, with a small amount of glue code to use serde_json, serde_urlencoded for body parsing and a very simple (and very fast) router of our own creation. This approach also made it very simple for us to introduce std-future/async-await in a gradual way.

mojzu 7y ago

I've been in the process of switching to tonic for the last few of weeks. Based on hyper/tower and has async/await support. It's a gRPC server rather than HTTP, so I've been using it with grpc-gateway to provide an HTTP OpenAPI v2 interface. It has automated quite a few things I found dull to do in other server frameworks, from the gRPC .proto file I can generate: - Rust server request/response types and request handler stubs. - grpc-gateway files and an OpenAPI v2 json spec. - Client side typescript types and request/response handlers from the OpenAPI spec. So now the process of adding a new endpoint is much less time consuming and involves writing less repetitive and error prone code. As mentioned above I've only been using it a few weeks but so far it has been great, easier to use than actix-web and felt no less responsive.