Design methods for multiple serialization targets/formats (not versions)
<p>Whether as members, whether perhaps static, separate namespaces, via friend-s, via overloads even, or any other C++ language feature...</p>

<p>When facing the problem of supporting multiple/varying formats, maybe protocols or any other kind of targets for your types, what was the most flexible and maintainable approach? </p>

<p>Were there any conventions or clear cut winners?</p>

<p>A brief note why a particular approach helped would be great.</p>

<p>Thanks.</p>

<p>[ ProtoBufs like suggestions should not cut it for an upvote, no matter how flexible that particular impl might be :) ]</p>
