Is it fine to have multiple RequestResponse fields in a single network behaviour struct?

[tqwewe]

Is the following network behaviour struct problematic given the two RequestResponse fields?

#[derive(NetworkBehaviour)]
struct Behaviour {
    foo: libp2p_request_response::cbor::Behaviour<FooReq, FooResp>,
    bar: libp2p_request_response::cbor::Behaviour<BarReq, BarResp>,
}

enum FooReq { }
enum FooResp { }
enum BarReq { }
enum BarResp { }

Will the request responses correctly work together without messages being mixed between them causing issues?

The reason I ask, is that from an ergonomic perspective, it drastically simplifies an API for my crate if its fine to do something like this.

[romac]

It should be fine as long as you construct each behavior with a unique StreamProtocol so that libp2p can associate a separate stream with each one.

[dariusc93]

Yes its fine to have multiple request response behaviour. Like @romac said, they would need to have their own unique protocols.