Thomas Eizinger comments

Results 1888 comments of


                                            Thomas Eizinger

Hole-punching tutorial: ListenerClosed before learning external address

Let me know if this is still an issue.

Rename `Swarm` to `Switch` due to changing specification naming.

I think `go-libp2p` calls this `Host` so this might be a good candidate.

Rename `Swarm` to `Switch` due to changing specification naming.

Closing as stale.

Add a streaming-response protocol to rust-libp2p

> While exploring some ideas and getting to know libp2p internals better, I ended up implementing a `NetworkBehaviour` that simply exposes the raw `AsyncRead + AsyncWrite` substreams to higher-level code....

Add a streaming-response protocol to rust-libp2p

> > If I can ask, what do the protocols look like that you are building @Frando? > > One thing I'm looking into at the moment is a simple...

Add a streaming-response protocol to rust-libp2p

I think looking at it holistically, we have the following choices when it comes to making people's life easier for writing their own protocols: 1. Re-think the abstractions of `NetworkBehaviour`...

#[derive(NetworkBehaviour)] doesn't work as documented when out_event is set

Closing as stale.

Missing cmake

Fixed in https://github.com/libp2p/rust-libp2p/issues/3024.

Refactoring: Drop custom `Either` types where possible

I opened an issue with `either` to see if we can get `AsyncRead` + `AsyncWrite` traits. Then we could drop the `EitherOutput` type: https://github.com/bluss/either/issues/79

Refactoring: Drop custom `Either` types where possible

> I opened an issue with `either` to see if we can get `AsyncRead` + `AsyncWrite` traits. Then we could drop the `EitherOutput` type: [bluss/either#79](https://github.com/bluss/either/issues/79) Update: As suggested in the...