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

Niclas Hedhman updated ZEST-102:
--------------------------------
    Fix Version/s: 3.0

> Custom (de)serialization mapping
> --------------------------------
>
>                 Key: ZEST-102
>                 URL: https://issues.apache.org/jira/browse/ZEST-102
>             Project: Zest
>          Issue Type: Improvement
>            Reporter: Niclas Hedhman
>             Fix For: 3.0
>
>
> Currently the Serialization subsystems are expecting that the deserializer is 
> reading the serializer's output, and what the format is, is largely out of 
> interest.
> But often, one wants better control of both input and output of the 
> serialization system, so that foreign protocols can easily be supported, 
> without writing the serialization from scratch for those cases.
> Inspiration should probably be found in Jackson, and perhaps(!) the answer is 
> more about providing a Zest-adapted plugin to Jackson and then use Jackson 
> internally everywhere in Zest. In any event, the fact that Jackson can be 
> extended in all kinds of fashion, should serve as the blue print for how Zest 
> achieves something similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to