If some application is offering subscribing, it finds or creates HttpClient and TcpClient after receiving the subscription.
HttpClient and TcpClient don't get deleted after receiving unsubscribe, and even receiving unsubscribe is not assured.
That might lead to constantly increasing numbers of HttpClients and TcpClients in the applications that are offering subscribing.
Solution: RO shall communicate de-registrations as broadcast.
ApplicationPattern has already been complemented by /v1/dispose-remainders-of-deregistered-application service.
[x] Addressing the /v1/deregister-application: service at RegistryOffice must result in sending a request to /v1/dispose-remainders-of-deregistered-application at all registered applications.
[x] The /v1/register-application: service at the RegistryOffice must be complemented by the a string attribute for informing about the /v1/disregard-application: service at the registering application.
Making the de-registration being part of the ApplicationPattern might make some individual implementations obsolete
[x] Corresponding services shall be marked "deprecated".
openBackhaul
commented
9 months ago
see also ApplicationPattern Issue #686.
If some application is offering subscribing, it finds or creates HttpClient and TcpClient after receiving the subscription. HttpClient and TcpClient don't get deleted after receiving unsubscribe, and even receiving unsubscribe is not assured. That might lead to constantly increasing numbers of HttpClients and TcpClients in the applications that are offering subscribing.
Solution: RO shall communicate de-registrations as broadcast.
ApplicationPattern has already been complemented by /v1/dispose-remainders-of-deregistered-application service.
[x] Addressing the /v1/deregister-application: service at RegistryOffice must result in sending a request to /v1/dispose-remainders-of-deregistered-application at all registered applications.
[x] The /v1/register-application: service at the RegistryOffice must be complemented by the a string attribute for informing about the /v1/disregard-application: service at the registering application.
Making the de-registration being part of the ApplicationPattern might make some individual implementations obsolete