I just mean that if we want plugin components to return JSON instead of using the proposed mechanism, than people programming plugins would not be able to return a dict() and have it rendered by a view as they are used to, we would have to create a new programming paradigm and new functions (API) to deal with it.
I think the proposed system is minimally disruptive, programmers do not need to know anything about AJAX/JSON and I should be able to handle it with a single new chapter in the book. ;-) Massimo On Oct 1, 10:03 am, Pynthon Pynthon <forumx...@gmail.com> wrote: > Maybe I did not understand the word API but that means you need to rebuild > everything? Or do you mean a new json API? > > Sorry :$. > > 2009/10/1 mdipierro <mdipie...@cs.depaul.edu> > > > > > One rarely needs to return metadata (js/flash) with response and with > > the proposed mechanism one would not need any special API to create a > > plugin. If using json the response would have to be encoded in json > > and this would require new api. > > > On Oct 1, 9:25 am, AndrewLoot <andrew.luetg...@gmail.com> wrote: > > > Whats the benefit of using headers for inter-component communication > > > why not pass a json object in with the response? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
