> > In general, when looking at angular.js and ractive.js doc, it seems like > there's a push to move more functionality to the client side. This seems > counterproductive for a couple of reasons. The clients are far less capable > than the server ... think cell phone ARM processor with a few MB memory vs. > server pentium with many GB memory. So isn't pushing more processing onto > client going to slow down the user experience and eat up mobile device > battery faster? Isn't it more efficient to do the processing on the server > and then send a few kb down to client end? >
Yes, each client is (generally) less powerful than your server, but your server has to process requests for *all *clients, whereas each client has to handle only its own content. It's also faster for the server to return a small amount of JSON data (which the client can then use to update the DOM) rather than a full HTML response (i.e., less network traffic). Anthony -- 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.
