All geek questions in one place

GWT webpage complexity

I use the Google Web Toolkit (GWT) to implement a sophisticated web application. I was wondering, however, how many components can be included in one page (aka entry point) before the browser becomes unusually slow? Can I better split the application into several small web pages?

+3
source share
5 answers

I would see how your users actually use the site.
If you find a good separation of GWT applications (each user sticks to their small GWT application), then I don’t understand why you cannot separate them.
If, however, you find that your users are constantly switching from one application to another and impose the overhead of running another application, then you might want to consider one monolithic application. I would be inclined to this approach, unless, of course, you are doing very intensive applications. I doubt that browsers will have many problems with highly optimized JavaScript GWT.

+2
source

I'm more concerned about usability than resources.

, . , .

. , , SO, , . .

+1

, , ...

  • ... , .
  • ... , , - . .

GWT, . , .

+1

, . , . , , , - , .

+1

- DOM - , div. div . , , , -, . , . .

0

Source: https://habr.com/ru/post/1722701/

More articles:


All Articles