231 discover feature protocol

[Christiantyemele]

This is a discussion

As from the spec here: we will need to have a way to know in real time what protocols our mediator supports and is willing to disclose, From our previous disscussion i think we brought out a way which could help, were we said the protocols will be loaded in a hashmap, i thought of search for the protocols to disclosed in that hashmap, I am not a 100% sure its the best way to it but for now its the only way i see, But i will need to collaborate with @Hermann-Core and @ndefokou if that be the case.
Right now i have done a version taking aside the above suggestion and used a mock, but i'ld still like the implementation to be checked

Emphasise should'nt be laid on the test for now its not complete !

[Christiantyemele]

_ No description provided. _

[Hermann-Core]

As from the spec here: we will need to have a way to know in real time what protocols our mediator supports and is willing to disclose, From our previous disscussion i think we brought out a way which could help, were we said the protocols will be loaded in a hashmap, i thought of search for the protocols to disclosed in that hashmap, I am not a 100% sure its the best way to it but for now its the only way i see, But i will need to collaborate with @Hermann-Core and @ndefokou if that be the case.

Protocols should be separate and not directly communicate with each other. We need a method to identify supported protocols. Currently, we have a couple of solutions:

• Reading the manifest file of the didcomm-messaging plugin to get the declared features, although:
  • It doesn't provide the versions of the supported protocols.
  • Some protocols may be intentionally omitted during the loading of the mediator server.
• Adding the collected protocols into the AppState, thus, the handler can access and identify the mounted protocols.

[Blindspot22]

I will approve these after the conflicts have been solved.

[Hermann-Core]

Please merge the main branch to yours.