in a near future if you need to play with command pattern you could find some interesting hints with thoses articles : - Tutorial explaining the basics of gwt-dispatch : http://borglin.net/gwt-project/?page_id=283 - Nice articles about batching with gwt-dispatch (by the M. David Chandler) http://turbomanage.wordpress.com/2010/07/16/dispatchqueue/ http://turbomanage.wordpress.com/2010/07/12/caching-batching-dispatcher-for-gwt-dispatch/
PS it's always good to keep in mind browser's limitation but the limitation of '2 connection /server' tend to move to more ajaxfriendly values with the newest version of FF, IE ... Browser HTTP/1.1 HTTP/1.0 IE 6,7 2 4 IE 8 6 6 Firefox 2 2 8 Firefox 3 6 6 Safari 3,4 4 4 Chrome 1,2 6 ? Chrome 3 4 4 Opera 9.63,10.00alpha 4 4 source : http://www.stevesouders.com/blog/2008/03/20/roundup-on-parallel-connections/ PS N°2 maybe the user won't hit the 2nd or 3rd tab, you should consider calling RPC only if needed On 1 sep, 14:45, Fabian <fabi.gin...@web.de> wrote: > Hi Tanguy, > > thank you for your answer. I think for my app it is too late to switch > to this kind of using commands and due to that having the chance to > batch them. (since i have only a few days to finish it). I will > consider it in my next apps. > > Thanks for telling me, that fewer rpc calls are better than more rpc > calls (considering same amount of data), didn't find this information > anywhere! > > I think for my app i will just wait until the first rpc send the data > from the server to the first tab, and then start the other rpcs. That > should be good enough for my app this time. > > Greetings, > Fabian -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.