Have you looked at breezejs? A "JavaScript library that helps you manage data in rich client applications".
Breeze dynamically builds a mirror of the server-side db model on the client and then binds to UI controls so the UI updates when the data model changes. Each object knows when it has changed and what has changed. Essentially it builds a client-side cache of the db. On the surface it's focused on .NET (with it's own .NET components), but if you look underneath you see that web2py could easily provide the back-end. Nice overview here: http://www.breezejs.com/documentation/introduction MIT license. On Saturday, June 21, 2014 9:33:04 PM UTC+12, Massimo Di Pierro wrote: > > web2py is mostly serverside and that is not going to change. I think what > we are discussing is the future... > > In the future I envision a new framework that has more client-side logic. > In order to do that we have make some choices of client-side frameworks. I > also agree that communication between client and server needs to rely on > standards. One possible standard are using hypermedia API for self > documenting json services. Yet I find it to be insufficient. I am spending > lot of time thinking about a generic way for client and server to > communicate. The problem is that they need to communicate more than data, > but also templates, and workflow information. > > > On Friday, 20 June 2014 16:26:44 UTC-5, Phyo Arkar wrote: >> >> >> On Sat, Jun 21, 2014 at 3:31 AM, Michele Comitini <[email protected] >> <javascript:>> wrote: >> >>> My POV is that web2py should have a rather agnostic attitude toward a >>> wide range of frameworks, by having some kind of layer that would allow to >>> keep server side code mostly untouched when changing js framework, easily >>> add support for a new js framework. >>> In practice web2py should use a well defined protocol between client and >>> server, to pass actions, messages and events back and forth. >>> >> >> >My POV is that web2py should have a rather agnostic attitude toward a >> wide range of frameworks, by having some kind of layer that would allow to >> keep server side code mostly untouched when changing js >framework, easily >> add support for a new js framework. >> >In practice web2py should use a well defined protocol between client and >> server, to pass actions, messages and events back and forth. >> >> >> + 100! >> >> Exactly my toughts too. >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
