I've been thinking about browser-server data sync for use in my next project. Sync is potentially more interesting than RPC style ajax, especially for rich clients, and I think sync could be a grand thing to add to lift.
The basic idea is like this. A javascript client subscribes to a set of syncable objects. The objects are then mirrored on the client and the server. Modify a syncable object on the server and the changes are pushed via comet to the client. Modify a syncable object in javascript, and the changes propagate to the server. I've did some sketches on the javascript side, and I think it'll be a nice fit there. Saving changes made on the browser becomes more transparent in the same way that ORM/JDO makes persisting to a db simpler. And rich clients can reuse change notification rather than creating custom ajax endpoints for server push. Adobe has a Data Management Service<http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/lcds/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Parts&file=data_manage_4.html>on this theme. I'm not sure what the closest thing in the java world would be. Perhaps browser sync would fit in lift as an alternate backend to record/mapper? Lee --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
