The Middleware is now capable of routing traffic to multiple network applications simultaneously through the WebSocket protocol. The new routing mechanism is using subdomain names and enables independent connection with the network applications. The Middleware is not capable to host domains, therefore, the additional configuration of a CoreDns server has to be realised separately (documentation will be provided).
Within this branch, other minor fixes for deploying multiple Middleware instances have been addressed.
Fixes #198
Type of change
[x] Bug fix (non-breaking change which fixes an issue)
What has been changed?
Fix: Subdomain based network applications routing
Fix: Minor fixes for multiple Middleware instances deployment
How Has This Been Tested?
[x] Test A - Routing to multiple network applications - successful
[x] Test B - Multiple Middleware instances deployed with synchronised backing services under a single organisation - successful
Checklist:
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
Description
The Middleware is now capable of routing traffic to multiple network applications simultaneously through the WebSocket protocol. The new routing mechanism is using subdomain names and enables independent connection with the network applications. The Middleware is not capable to host domains, therefore, the additional configuration of a CoreDns server has to be realised separately (documentation will be provided).
Within this branch, other minor fixes for deploying multiple Middleware instances have been addressed.
Fixes #198
Type of change
What has been changed?
How Has This Been Tested?
Checklist: