You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2017/03/07 11:06:38 UTC

[jira] [Resolved] (SLING-6325) Split Avro and Kryo serializers into their own bundles

     [ https://issues.apache.org/jira/browse/SLING-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tommaso Teofili resolved SLING-6325.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Content Distribution Extensions 0.1.0

> Split Avro and Kryo serializers into their own bundles
> ------------------------------------------------------
>
>                 Key: SLING-6325
>                 URL: https://issues.apache.org/jira/browse/SLING-6325
>             Project: Sling
>          Issue Type: Task
>          Components: Content Distribution
>            Reporter: Tommaso Teofili
>            Assignee: Tommaso Teofili
>             Fix For: Content Distribution Extensions 0.1.0
>
>
> A while ago we created the _sling.distribution.extensions_ bundle to host some PoCs for SCD extension points.
> Now that the {{DistributionContentSerializer}} API is exposed it'd be probably better to create two separate bundles for Kryo and Avro serializers as it's more likely that people will only use one of those serializers only, also for decoupling and separation of dependencies concerns.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)