Skip to content
This repository has been archived by the owner on Mar 6, 2023. It is now read-only.

Support of Alternative Encoding Format #71

Closed
aidmony opened this issue Dec 20, 2017 · 1 comment
Closed

Support of Alternative Encoding Format #71

aidmony opened this issue Dec 20, 2017 · 1 comment

Comments

@aidmony
Copy link

aidmony commented Dec 20, 2017

Hi,

I am trying to add support (a new custom plugin) for alternative encoding format such as flatbuffer. There is a difficulty of supporting these encoding format, because they do not have switch cases in the decoding / encoding process. I am currently thinking of two possible solutions: 1) creating additional classes for each subtype, and then encode/decode an _adtObject (this will be casted to different subtype classes) instead; 2) simply encode/decode every declared properties.

Please let me know which approach will you recommend. Thanks!

@calimarkus
Copy link
Contributor

How would you implement it without remodel? Remodel shouldn't limit your decision here. You can write a plugin that works either way.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants