Organising option flags about go-libp2p-daemon HOT 4 OPEN

This is nice for testing. We should also have a flag that specifies the listen addresses, so that we can only listen on QUIC for example but still be able to dial tcp.

from go-libp2p-daemon.

Its nice, but i think WebSockets transport could not work without TCP transport and QUIC transport could not work without UDP transport.
Also from my early experiments there not so many nodes in network which support something different from TCP, So i think this options can be useful only when network will be able to satisfy it.

from go-libp2p-daemon.

It's pretty nice to me. If there are too many combinations of the flags in a namespace, does it make sense to have something like -tpt="tcp,ws", and the argument parser handles the logic?

from go-libp2p-daemon.

I like this approach, I think it would be great to get spec'd out. When implementing the js daemon I referenced the cli parser of the go implementation, but it would be great to see that externalized as a spec. This will also ensure our interop testing is a lot easier if we can just leverage the same flags consistently.

If there are too many combinations of the flags in a namespace, does it make sense to have something like -tpt="tcp,ws", and the argument parser handles the logic?

I'd like to see us leverage something like #63 to overcome the large number of flags problem. I think it's a nice approach for running more customized nodes.

from go-libp2p-daemon.