Trait Transceiver is not public

[cBournhonesque]

Trait Transceiver is not public

[benny-n]

Hi @cBournhonesque

This trait's main purpose was to allow easy and modular testing and I didn't think it would be of any use as public, that's why the module was made private.

Having said that I see no problem at all in making it public :)

Out of curiosity, could you elaborate about your specific use-case?

[cBournhonesque]

I wanted (just to learn rust + networking) to create a networking library where I would work on passing messages reliably + fragmentation (equivalent of reliable.io if I understand correctly), but use your library for all the logic of establishing a secure connection (equivalent of netcode.io).

I'd like my library to be transport-agnostic so that I could potentially use transports that are compatible with browsers via wasm (webtransport or webrtc, potentially?)

Here's an inspiration which is transport-agnostic! https://github.com/naia-lib/naia/tree/main

[benny-n]

Sounds great!

FYI, I plan to implement a reliable.io layer as a feature for this crate (when I'll have some extra time to spare).

Until then, I will start working on making Transceiver public.
Turns out it won't be as straight forward as just adding pub to the module. Currently there is no easy way to obtain a Client or a Server with a custom Transceiver at all, since new is only implemented for Server<NetcodeSocket> and Client<NetcodeSocket>.

My current plan is to generalize most of the behavior in those implementations and add a with_custom_transceiver method to both Client and Server.

[cBournhonesque]

Awesome; is there a way I could chat with you? Maybe on discord?

[benny-n]

Sure :)
My discord is wicked_lama

[benny-n]

@cBournhonesque I opened #8 to address this issue.
It would be great if you could try it out and see if it suits your use case!