The conclusion I came to was that in writting Business Applications with a Rich Client interface we needed to tweak the MVC paradigm. I am working on javaclient.sourceforge.net (there is only stuff in CVS, basic example, putting together Web pages today as we speak.) My thought is to split the Controller into a Client Side and a Server Side, with the model getting replicated at client and server transparently using the JBoss invoker stack. The Server side being represented by a SSB. So the business logic updates the Server side model which then gets updated on the Client and propigates out to the view. That way the minimum amout of data is moving back and forth.
I looked at using JBossCache to represent the model, but there are a couple of cases where you just want the data to flow through and not be saved. For example if you are browsing a customer list in a table you really only want to ship the data across the wire and view it. Then on each line store the primary key for the line and ship that back when the line is selected. I think the bigger issus is that the model only needs to be synchronized when a Server Controller method is called. Otherwise the data can just sit on the client and only be updated when it is needed on the server. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843532#3843532 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843532 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
