The approach is correct IMHO, not only for forms. DOM is client's matter and by the way gives a nice level of abstraction over everchanging DOM implementations of clients. What eventually will be extended is the JSON dialect. There is a little overhead in the JS machinery on the clients that needs to be adapted and mantained, but it is a smaller issue than that of server side generated DOM. I suspect that the approach will be successful even on non-html devices.
mic 2014-09-08 21:09 GMT+02:00 Leonel Câmara <leonelcam...@gmail.com>: > My experience is that it's faster on the client side too unless you have a > pretty good 3G connection (or even better 4G). > > That said, the scalability and hardware savings advantage on the server > side is unquestionable. You don't have to cache pre-rendered HTML and you > finish requests quicker. > > -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
