>> As for dates - why not just encode them as strings? >OK, but i think that also for performance reason this should be better ...
OK, how about longs, then? >So at concept level, if i could attach optional handlers (my classes >extending a base Pivot class or interface for this) for >serializing/deserializing some my classes, i could give to the >serializer the real data without making conversions (that would be >done by handlers inside the Serializer and only if enabled and for >example after an exception). That does seem a bit complex. To me, this type of requirement implies that perhaps JSONSerializer is not the right choice for your application.
