Why ILocalPeer.DiaAsync is incompatible with ISessionProtocol<'req, 'res>

[Xyncgas]

If I created custom protocol that's a 'ISessionProtocol' I can use ILocalPeer.DialAsync() and it works

But ILocalPeer.DialAsync fails if is ISessionProtocol<'req, 'res>

The specialization is asymmetric protocol in nature and apparently it allows passing a request to DialAsync which's handy sometimes and I understand it's unmagical and can not serialize anything I requested to the remote machine and it's simply a request passed to the DialAsync method itself which I should implement in the protocol implementation if I want any serialization or something I should accomplish, and can use it still for yielding the request-response control flow out of the handler for protocol's DialAsync/ListenAsync, for now I can work around by converting ISessionProtocol<'req, 'res> to ISessionProtocol myself (Apparently can not)

[Xyncgas]

Although I realized ILocalPeer.DialAsync is callable in both ILocalPeer.DialAsync and ILocalAsync.DialAsync(request)
The latter implies you're interested in calling an Asymmetric protocol you had built the ILocalPeer with and it's automatically selecting the proper protocol for the proper protocol (if you registered various protocols in building ILocalPeerFactory) for you

[Xyncgas]

But I can not wait for ISession.DialAsync(request) to return after geting the ISession object from ILocalPeer.DialAsync
how can I get ISessionProtocol<'req, 'res> working?

[Xyncgas]

I figured out, the proper way for calling ISession.DialAsync(request) using Asymmetric protocol is ISession.DialAsync<ISessionProtocol<'req, 'res>, 'req, 'res>(request)
I would be hoping in the future ISession.DialAsync simply takes an optional parameter called request, since usually ILibp2pPeerFactoryBuilder has the protocol added and generates IPeerFactory which generates ILocalPeer which generates ISession. If needed I guess several solution can consolidate the experience :

A

1. ISession.DialAsync(Type protocol, ?request) can be a thing
2. ISessionProtocol<'req, 'res> and ISessionProtocol becomes abstract class and sharing IAbstractSessionProtocol for ISession.DialAsync
3. By magic ISession.DialAsync(?request) works and ISessionProtocol<'req, 'res> or ISessionProtocol provided to ILibp2pPeerFactoryBuilder recognize it

ISession.DialAsync can return either exception or result that might exist because Symmetric protocols do not have the return

B

People create Wrapper class and Wrapper<'request, 'response> specialization which handles Symmetric and Asymetric ISessionProtocol Separately

[Xyncgas]

dotnet-libp2p/docs/README.md

Line 48 in a3d1c58

int answer = await remotePeer.DialAsync<SomeProtocol, string, int>("what is answer to the Ultimate Question?");