Are GWT 2.1.1 Activities expensive to create ? Activities are managed by ActivityManagers. ActivityManagers call "start" method on Activities so that Activities can start doing their work. Activities do majority of their work in their start method, for example communicating with the server, populating views with data and so on.
having said all these, Activities can take PlaceController, Place, Presenter objects in their constructors. therefore even if they are not "Started" by the ActivityManager, just instantiation of them can be costly. is this true ? my main concern is this: lets say an application has 150 activities. and application is configured in such a way in GIN, that all of application activities are injected in a provider on application startup. therefore all of the 150 activities are instantiated, however they are not started yet (activitymanager has not called the start on them). I want to know whether this early eagerly instantiation is expensive and will bring down the application ? if the activities were "Started" on startup, which resulted in contacting server for data, I can imagine it can become slow as application grows. Do you think even the instantiation of activities is expensive ? consideriing an Activity has a Place, PlaceController, a View and a few Presenters. (therefore activities have dependency of their own) Thank You -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
