On Thu, Apr 30, 2009 at 4:07 PM, Guus Bloemsma <[email protected]> wrote:
> Obviously there is no point in running all of Qi4J on the browser. Low level > layers like persistency would be possible by proxying but that could involve > lots of roundtrips which is exactly what you want to avoid to get a smooth > GUI. FYI, there are not "a lot of round-trips" in the "persistence" layer... > The user can then work in that GUI and manipulate the entities. The > underlying Property objects keep track of get()s and set()s to record a UoW > which is sent back to the server when something is committed. ... and this is effectively 'everything' regardless of whether you run a 'local' JDBM instance or the remote Rest system. So, I am not sure what will not end up on the client, except some of the extensions. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
