Hi, Am 27.04.2012 um 12:39 schrieb Jukka Zitting:
> For example (and I know this has been discussed at length already), > much of the path and json/p handling code shared between -core and -mk > is just there to first generate jsop strings and then parse them > again. It's obviously good to avoid duplicating such code, but even > better if we could avoid it in the first place. Which would be an argument of non-stringly typed MK API and leave serialization stuff to be internals of any MK API implementation -- be it for actual persistence or for a remoting layer... Regards Felix
