>> as you have discovered, there are issues when converting to formats like JSON. >> Agreed - In an 'Ajaxy' web world it it important to 'play nice' with things like json and making this clean this should not be an afterthought. (FWIW/BTW If I were comparing frameworks for serious Web development (I'm not) this sort of wart would likely steer me away from the framework as I would expect heavy ajax/json usage on any interactive website).
My concern is not that there is no workaround - it's more that no one seems to have foreseen and/or documented potential issues re the using json and computed results. After 4/5 years of development I can't be the first person to deal with this issue. (Massimo's earlier response indicates (to me) that he is clearly thinking server side, but perhaps has not fully considered the end to end solution). >From a practical standpoint maybe some beefing up of the json section of the docs would be helpful. Right now I'm building a small demo app using dojo, ajax and web2py - I'll be happy to share any useful code samples when I'm a bit further on with my project. BrendanC
