mmm.... the main idea of REST is to start black boxing functionality. Which is kinda great but has down sides of performance (as noted in the url that Yarko tendered) The theoretical world does need to be tempered with practical applications often.
As in RoR convention over configuration is a major factor. (That means that a function is pre configured with a way of acting. ie index() is a create form action) I think Massimo is using this approach in designing web2py, but I think it is up to us to give him feedback on whether we think his design assumptions are the right pre configuration for the majority of developers. If the majority of us think that displaying a list of records for a table is the default index behaviour rather than a create form then Massimo should feel the weight of this feedback. Ther are other things to consider for a framework developer (like compatibility backward etc) but there is power in developing in this sort of community as our collective experiences bring out more goals that can be achieved with the framework. my 2 cents Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
