This is how I see it (at least conceptually) : Servlets/JSP are request based (synchronous access) and need to pull data from the model. In a stand alone app (typically Swing), remote or not, something must trigger (pull) the request, but you can do this asynchronously so the view dont have to block waiting for the response. Then you can have the view being registered as listeners to the model being updated. Hence a concept of data being pushed to the gui. Right ?
regards > > Nothing :) Swing app & web frontend are quite > different in nature. Web one lives from request to > request - you got request, you have to gather data > together ( we do not speak about frameworks now ), > you have to render response. > In a swing there are much more things to worry > ( you basically got a lot of components, which need > data and you have to optimise remote calls ) > ------------------------------------------------------- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
