Does ENet application compatible with another application written by original UDP?

[xpbigapple02]

I have been read some docs about ENet, ENet don't integrate TCP and UDP, It uniform protocol layered over UDP to the developer with the best features of UDP and TCP as well as some useful features neither provide. I have little confused:

Does Enet have special self-custom data struct in application layer protocal, or does it do these under application layer, so user will be used in transparent mode?

Two application written by ENet using reliable udp (server,client) should be work fine, but is it fine as change one to original UDP?

I just need a usable reliable UDP library can working with another UDP server or client, may be they have reliable or none reliable(original UDP), ENet suitable?

[dimage1]

Hi, you need to use the same protocol on both communication sides. ENet works above UDP, adding extra rules, data structures and logic to support reliability, channels, security, etc.

If you want another UDP based protocol, please look at QUIC, which is now rfc9000 and is used by modern browsers as HTTP3 transport.