遗留应用程序中具有多个主机页面的GWT-GWTwithmultiplehostpagesinalegacyapplication

5  

One of the ways GWT was designed to be used is exactly as you've used it. We have done that in many of our apps - where there is one GWT module with multiple 'parts' that are loaded based on whether a given id exists on a page or not. So I don't see that you'll have any issues at all going this way. We often use this approach even for new web applications, where we just want a few 'widgets' on the page, rather than coding the whole application in GWT.

设计使用GWT的方法之一与您使用它完全一样。我们已经在许多应用程序中完成了这项工作 - 其中有一个GWT模块具有多个“部件”,这些部件是根据页面上是否存在给定ID而加载的。所以我没有看到你这样做会有任何问题。我们经常使用这种方法甚至用于新的Web应用程序,我们只需要在页面上使用一些“小部件”,而不是在GWT中编写整个应用程序。

It won't make a huge difference, but one thing I would suggest is not putting the GWT Javascript code into your main template, but rather only put it on the pages that need it. It's true that if you're not running HTTPs it is cached basically forever, but it seems wrong to get people to load in the module if it's not actually needed on that page. This of course depends on how people use your site, if they are likely to download it anyway then it won't make any difference.

它不会产生巨大的差异,但我建议的一件事是不将GWT Javascript代码放入主模板,而只是将它放在需要它的页面上。确实,如果你没有运行HTTP,它基本上是永久缓存的,但如果在该页面上实际上不需要人们加载模块似乎是错误的。这当然取决于人们如何使用您的网站,如果他们可能会下载它,那么它将没有任何区别。

2  

You're doing it right. Avoid avoid avoid the temptation to try to 'minimize' the GWT footprint by breaking it up into multiple separate apps.

你做得对。避免避免试图通过将其分解为多个单独的应用程序来“最小化”GWT足迹的诱惑。

The key to GWT performance is to have as few downloads as possible and to make sure they're cached. Loading a 250k bundle once is much better than two 200k bundles and because compression get's better with larger files you really start to reap benefits as things grow.

GWT性能的关键是尽可能少地下载并确保它们被缓存。一次加载一个250k的捆绑包比两个200k的捆绑包要好得多,并且因为随着事情的发展,压缩对于更大的文件变得越来越好,你真正开始获益。

y-slow & firebug can be really helpful when it comes to convincing yourself of this.

y-slow&firebug在说服自己时非常有帮助。

One performance trick you might check out is available in the sample chapter here: http://www.infoq.com/articles/progwt It shows a mini-architecture around loading GWT widgets into any number of slots and pre-populating data in Javascript variables. This allows your GWT widgets to load and not require a second HTTP GET to get the data they use. In practice I found that this was a nice performance boost.

您可以查看的一个性能技巧可以在这里的示例章节中找到:http://www.infoq.com/articles/progwt它显示了一个迷你架构,可以将GWT小部件加载到任意数量的插槽中,并在Javascript中预先填充数据变量。这允许您的GWT小部件加载,而不需要第二个HTTP GET来获取他们使用的数据。在实践中,我发现这是一个很好的性能提升。