使用async(tokio)rust-websocket在客户端之间共享可变状态

时间:2017-07-03 02:20:41

标签: asynchronous websocket rust rust-tokio

我正在使用rust-websocket及其基于Tokio的异步系统在Rust中编写websocket服务器。我可以很好地为客户服务,但是,我无法弄清楚如何在客户端之间共享可变状态。以下是一些(部分)代码,用于演示此问题:

let mut core = Core::new().unwrap();
let handle = core.handle();
let server = Server::bind("localhost:62831", &handle).unwrap();

let mut state = State{
    ...
};

let f = server.incoming()
    .map_err(|InvalidConnection {error, ..}| error)
    .for_each(|upgrade, _)| {
        let f = upgrade.accept()
            .and_then(|s, _| {
                let ctx = ClientContext{
                    // some other per-client values
                    state: &mut state,
                }
                ...
                return s.send(Message::binary(data).into())
                    .and_then(move |s| Ok(s, ctx)); // this could be the complete wrong way to insert context into the stream
            }).and_then(|s, ctx| {
                // client handling code here
            });

            handle.spawn(f
                .map_err(...)
                .map(...)
            );
            return Ok(())
    });

core.run(f).unwrap();

此代码错误:

error[E0373]: closure may outlive the current function, but it borrows `**state`, which is owned by the current function
   --> src/main.rs:111:27
    |
111 |                 .and_then(|(s, _)| {
    |                           ^^^^^^^^ may outlive borrowed value `**state`
...
114 |                         state: &mut state,
    |                                     ----- `**state` is borrowed here
    |
help: to force the closure to take ownership of `**state` (and any other referenced variables), use the `move` keyword, as shown:
    |                 .and_then(move |(s, _)| {

在尝试编译器的建议时,我明白了:

error[E0507]: cannot move out of captured outer variable in an `FnMut` closure
   --> src/main.rs:111:27
    |
111 |                 .and_then(move |(s, _)| {
    |                           ^^^^^^^^^^^^^ cannot move out of captured outer variable in an `FnMut` closure

error: `state` does not live long enough
   --> src/main.rs:114:37
    |
114 |                         state: &mut state,
    |                                     ^^^^^ does not live long enough
...
122 |                 })
    |                 - borrowed value only lives until here
    |
    = note: borrowed value must be valid for the static lifetime...

我还尝试将状态包装在RefCell中(在状态本身之后立即创建RefCell),然而,编译器发出类似的移动错误,因为它试图移动{{1}进入创建客户端上下文的闭包。

1 个答案:

答案 0 :(得分:1)

你与RefCell非常接近。您现在需要的是Rc来包裹RefCell,以便您可以克隆Rc而不是捕获RefCell本身。

let shared_state = Rc::new(RefCell::new(State::new())));
incoming().for_each(move |s, _| {
    let shared_state = shared_state.clone();  // Left uncaptured
    shared_state.borrow_mut().do_mutable_state_stuff(); // Could panic
});

请注意,由于您现在正在使用RcRefCell,因此您可能需要继续将ClientContext结构转换为存储Rc>而不是&mut State。对于某些事情,可能会继续使用&mut State,但您的&mut State将与RefMut的生命周期相关联,如果您保持活着直到下一个关闭运行,借用将会出现恐慌(如果使用try_变体,则会失败)。

另外请记住,如果您决定要在反应堆中拥有多个线程,则只需将Rc更改为Arc,将RefCell更改为Mutex ,这是一种非常自然的转换。