polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niclas Hedhman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (POLYGENE-102) Custom (de)serialization mapping
Date Sat, 25 Mar 2017 09:01:41 GMT

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

Niclas Hedhman updated POLYGENE-102:
------------------------------------
    Description: 
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 Polygene-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 Polygene achieves something similar.

  was:
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.


> Custom (de)serialization mapping
> --------------------------------
>
>                 Key: POLYGENE-102
>                 URL: https://issues.apache.org/jira/browse/POLYGENE-102
>             Project: Polygene
>          Issue Type: Sub-task
>            Reporter: Niclas Hedhman
>            Assignee: Paul Merlin
>             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 Polygene-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 Polygene achieves something similar.



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

Mime
View raw message