On Fri, Jun 25, 2010 at 9:26 PM, marius.andreiana < marius.andrei...@gmail.com> wrote:
> Thanks André, good overview. > > > Code-Spliting reduce the amount of code downloaded by the browser, > > so your app start faster and if you user don't use the featuer x.y.z > > the code will never be download (even flash can't do that). > But any other front-end, generated by say php/asp pages, has this. If > you don't use the feature x.y.z (at /x/featurex.php), it's never > loaded :) > We're not talking about server-side class-loading. M. > > > On Jun 24, 7:34 pm, André Moraes <andr...@gmail.com> wrote: > > GMail isn't a GWT app, because GMail is older than GWT. > > > > But Wave is a much more complex app and is GWT. > > Not that Wave is more mature than GMail but it has much more features > > than GMail. > > > > For the large application problem... > > > > GWT is to build complex "apps" for the browser. Not complex sites... > > > > The major source of problems for web application is: > > > > Network latency > > Server latency > > Client latency (if you are using IE 6 or making really bad HTML + > > Javascript processing). > > > > For the network latency: > > You can't change the network which your user will use, so u solve > > this problem by reducing the use of the network, so the impact will be > > less in you app. > > GWT helps you with the ClientBundle (loads as much as possible in > > one single connection to avoid open/close of many connections). > > Code-Spliting reduce the amount of code downloaded by the browser, > > so your app start faster and if you user don't use the featuer x.y.z > > the code will never be download (even flash can't do that). > > Very Strong cache, so if you don't change your app the client don't > > download the code again. It simply uses the browser cache. And if you > > can afford a CDN it will be even faster. > > Other things that i don't remember now. > > > > For the Server latency: > > GWT provides facilities for the server if you use Java on the Server > > (GWT-RPC), if not GWT don't make your server processing better or > > easier. > > Since GWT generate static files, you can use Reverse Proxy (nginx > > for example) to handle the serving of static files, so your > > application is downloaded first from the ultra fast reverse proxy and > > only when you fetch data your application server will be activated > > > > For the client latency > > GWT statically analyze your code to avoid redundant calls and make a > > lot of inlined code, so your code will run faster (because it is > > smaller and inlined). Even inheritance, with some caution, will be > > inlined. > > GWT can use DefferedCommand (i don't know if it is the right name) > > but with this tool, you can split your larger block in a series of > > smaller processing that will not block the browser. This processing is > > serial, but let the browser handle events and layout things. > > With HTML 5 WebWorkers you can make parallel processing on the > > browser. I read something abount HTML 5 Linkers for GWT but never > > used. Anyway, it's very easy to write some JavaScript to use with > > WebWorkers. > > > > I don't remember anything else now, but I am sure there is much more. > > -- > 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<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
