[
https://issues.apache.org/jira/browse/SLING-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893181#comment-13893181
]
Stefan Egli commented on SLING-3367:
------------------------------------
[~marett], agreed.
If request-gzip is config-dependent (disabled by default, as you suggested)
then we should be fine.
Generally speaking the topology announcements can be large both ways, since the
topology connectors can be arbitrarily composed (eg in a tree-structure). So
gzipping the request too is important IMO. Unfortunately the discovery.impl
1.0.2 will respond with a 500 if it receives a gzipped request, instead of a
400 (will fix that too) - so a discovery.impl 1.0.4 will not be able to
seamlessly fall-back from gzip to plain. But as we'll have it configurable we
should be fine.
> gzip topology announcements
> ---------------------------
>
> Key: SLING-3367
> URL: https://issues.apache.org/jira/browse/SLING-3367
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Discovery Impl 1.0.2
> Reporter: Stefan Egli
> Assignee: Stefan Egli
>
> Currently topology announcements are sent as plain-text JSON. If used in a
> large setup, the announcements grow in size and it would make a lot of sense
> to gzip it.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
