Mailing-List: contact dev-help@sling.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sling.apache.org
Date: Wed, 5 Feb 2014 16:16:13 +0000 (UTC)
From: "Stefan Egli (JIRA)" <jira@apache.org>
To: dev@sling.apache.org
Message-ID: <JIRA.12692875.1391440157748.42479.1391616973951@arcas>
In-Reply-To: <JIRA.12692875.1391440157748@arcas>
References: <JIRA.12692875.1391440157748@arcas>
Subject: [jira] [Commented] (SLING-3367) gzip topology announcements
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SLING-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892272#comment-13892272 ] 

Stefan Egli commented on SLING-3367:
------------------------------------

One issue here is backwards compatibility: if a new gzip-ping discovery.impl client connects to an old discovery.impl servlet which doesn't understand gzip, it would likely reject the connector.

> 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)