![]() ![]() Even if you box the returned Future, you end up having to use futures::Either a bunch and when you mess it up you get tons of confusing errors filled with the huge inferred types. ![]() Right now it's a huge pain to have more than one return value in an Actor Handler, the functions that handle actor messages. My main pain point with it is the use of futures. I like it a lot and think the actor model is good fit for applications that don't fit well into a request lifecycle. I'm using both Actix and Actix web for a personal project. And I think websockets still require actors? Originally "Actix web" depended on Actix the actor library, but no longer. This is Actix the actor model library, not "Actix web" the web framework that's usually discussed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |