we have the following modules for abstracting TCP sockets that exchange Sv2 Messages:
server:tcp::encryptedserver::tcp::unencryptedclient::tcp::encryptedclient::tcp::unencrypted
right now, Sv2ServerService and Sv2ClientService use server:tcp::encrypted and client::tcp::encrypted, without support for the unencrypted flavors
ideally, this should be inferred from Sv2ClientServiceConfig and Sv2ServerServiceConfig
we have the following modules for abstracting TCP sockets that exchange Sv2 Messages:
server:tcp::encryptedserver::tcp::unencryptedclient::tcp::encryptedclient::tcp::unencryptedright now,
Sv2ServerServiceandSv2ClientServiceuseserver:tcp::encryptedandclient::tcp::encrypted, without support for the unencrypted flavorsideally, this should be inferred from
Sv2ClientServiceConfigandSv2ServerServiceConfig