My only problem is when we require somthing.json or something.xml we can customize how the output gets filtered (generic.json, generic.xml, etc.) but not the input. hence the input format must be taken care at the action level or at the crud function level. If we do the latter, the behavior cannot be easily be overwritten at the function level.
Is the current solution appropriate? Massimo On Jun 14, 4:08 pm, Fran <[email protected]> wrote: > On Jun 14, 9:56 pm, mdipierro <[email protected]> wrote: > > > I am thinking (experimenting) that as we can do read.json and > > select.json perhaps one should be able to do create.json and send the > > data using json format. > > This is definitely required. > > Currently I'm using ?format=json for my CRUD functions, but having > support within Web2Py could be nice :) > > F --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
