> Well, if the API expects JSON, then it can't require anything that > isn't representable in JSON. If the API doesn't take JSON directly, > then you obviously have the control to do what needs to be done client > side. There isn't anything more to it, it just doesn't make sense to > hack simplejson so that it doesn't produce JSON anymore. If you need > to produce something that isn't JSON, then you're doing something > wrong or you've chosen the wrong tools.
Hum. I agree that one _should_ stick to JSON the way it is most of the time. It will make for a better design, that's for sure. Yet as there is plenty of server-side rendered javascript that gets executed "as is", with all possible side-effects, I fail to see where this crosses a line that isn't acceptable under certain circumstances. But then your track record of javascript coding compared to mine is ... well, one can't compare what doesn't exist. I'm taking my first steps here. So maybe I'm seeing the light someday :) Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
