actix | Actor framework for Rust | Reactive Programming library

I finally found 2 solutions:

Look at the examples in the docs for Data. It seems you have to put your initialized struct in a Mutex and then add that to your App. Also beware that you need to include it in your path fn as a Mutex as well.

Try this:

Since functions can implement traits, the solution is to define a trait that represents "can serve as callback function" and then manually implement it for every function arity up to some large number of arguments. In actix, this is done by having .to(f) take something implementing the Handler trait:

In your case token is a local variable and a reference to it (&token) is definitely not with a static lifetime. The compiler error explains it and shows it to you.

You probably want to create a HeaderValue instance some other way, not via from_static. For example like this: HeaderValue::from_str(&token).

Solved it by wrapping the UdpSocket in an Arc and keeping the reference in the actor for later use. Using the socket to write messages works. The split stream used for the streamhandler needs no change, as it works as expected.

An async function returns a Future, you need to await the future to get the result. In your case the Responder:

I think there are 2 problems here:

• Looks like you forgot to add EXPOSE 8000 to your dockerfile.
• Since you forgot to add expose I supposed you also forgot to bind your port when running your image: docker run -p 8000:8000 image_name

After tweaking some things around, I got it working. Even from your previous question, the problem is how you are approaching the connection creation. A good reference is in the crate actix-web-actors where the pattern is something like: