WebTransport protocol for the relay server

[MrishoLukamba]

Description

Currently working with wasm p2p web clients along with native relay server if you want to work with webtransport on the wasm and on native relay it wont work, As the crate currently just support the browser end

Motivation

having websocket and webtransport allows much flexibility

Requirements

1. Wasm to relay communication

Open questions

No response

Are you planning to do it yourself in a pull request?

Yes

[MrishoLukamba]

Reference issue, where native WebTransport was not implemented
#2993

[dariusc93]

Hey @MrishoLukamba could you provide any logs or any informations showing that the browser-side doesnt work with relay when connecting and obtaining a reservation with the native side (which currently would only be js-libp2p and go-libp2p), just for information here for anybody seeing this issue before such feature or fix is in place?

[MrishoLukamba]

No I am referring to Rust libp2p.
Only Browser side webTransport is implemented but not on the native relay side

[MrishoLukamba]

and @dariusc93 how can a wasm browser based relay client reserve itself in relay server if it cant support listening to an address?

[dariusc93]

and @dariusc93 how can a wasm browser based relay client reserve itself in relay server if it cant support listening to an address?

the browser doesnt support opening sockets (hence why you cant listen on localhost, etc), but you can listen on relays with supported transports for the browser (ie in this case, web socket and possibly web transport) which is just establishing a reservation and transferring data between two peers through the relay.