It would be possibly to transform any public web request (except the ICCC request) into an ICCC message and therefore, use the load-balancing of ICCC. The called web handler must wait for the answer, because the provided response stream. This feature would enable the user to use any of the Ocean servers as front load balancer and use the others as back-end workers.
Is it possibly to add this feature without breaking current apps? Maybe add this as an optional function!
It would be possibly to transform any public web request (except the ICCC request) into an ICCC message and therefore, use the load-balancing of ICCC. The called web handler must wait for the answer, because the provided response stream. This feature would enable the user to use any of the Ocean servers as front load balancer and use the others as back-end workers.
Is it possibly to add this feature without breaking current apps? Maybe add this as an optional function!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It would be possibly to transform any public web request (except the ICCC request) into an ICCC message and therefore, use the load-balancing of ICCC. The called web handler must wait for the answer, because the provided response stream. This feature would enable the user to use any of the Ocean servers as front load balancer and use the others as back-end workers.
Is it possibly to add this feature without breaking current apps? Maybe add this as an optional function!
changed the description