Hello,
First, thank you for your work on exclave-core. The project is impressive, and the additional outbound protocol support is genuinely valuable for many users.
However, there is a major limitation preventing exclave-core from being used in real deployments:
All newly added protocols currently support outbound only, with no inbound implementation.
This means exclave-core cannot function as a server for these protocols, and therefore cannot be deployed on the server side in any practical scenario. Many users — myself included — would like to run exclave-core as a full server with inbound support for the protocols you have added.
Request
Would you consider adding inbound support for the newly integrated protocols?
Even minimal inbound support would make exclave-core usable as a standalone server, significantly expanding its usefulness and adoption.
Your work is appreciated, and inbound support would make exclave-core a complete and deployable solution.
Thank you for your time and effort.
Best regards.
Hello,
First, thank you for your work on exclave-core. The project is impressive, and the additional outbound protocol support is genuinely valuable for many users.
However, there is a major limitation preventing exclave-core from being used in real deployments:
All newly added protocols currently support outbound only, with no inbound implementation.
This means exclave-core cannot function as a server for these protocols, and therefore cannot be deployed on the server side in any practical scenario. Many users — myself included — would like to run exclave-core as a full server with inbound support for the protocols you have added.
Request
Would you consider adding inbound support for the newly integrated protocols?
Even minimal inbound support would make exclave-core usable as a standalone server, significantly expanding its usefulness and adoption.
Your work is appreciated, and inbound support would make exclave-core a complete and deployable solution.
Thank you for your time and effort.
Best regards.