Integrate the possibility to compress messages into the Discovery Proxy

[surgitaix]

Currently, only Consumer and Provider communication is compressable. However, especially for the Discovery Proxy zip compression is a very useful feature. With many Providers registered at a DP, the list of available Providers inside a ProbeMatches message will be huge and many entry fields very similar to equal inside this list. Zipping will lead to a strong reduction of the data size.

[PaulMartinsen]

Isn't the ProbeMatches a response to the HTTP Probe request? If the request includes the Accept-Encoding with gzip then I think the discovery proxy is free to compress the response.

Or did I misunderstand the issue?

[surgitaix]

We rechecked. You are right:
R0005
In its role as an HTTP client, a SOMDS Participant should request gzip compression by using Accept-Encoding with "gzip".

That also covers DPs.

What remains is the subscription mechanism. It might not be as relevant since the reports will be shorter (each covering a Hello / Bye) message. But we should still discuss if we want to include it. This is how it is defined for Providers:

R0006
If a SOMDS Consumer includes an Accept-Encoding header field in an HTTP header in a WS-Eventing Subscribe request, the SOMDS Provider may transmit Notifications related to that subscription encoded with the encoding that was defined in the Subscribe request.

We could just extend the requirement to also cover DPs.