thank you for the very clear answer!

On Jun 2, 10:51 am, Sripathi Krishnan <[email protected]>
wrote:
> You have two options -
>
>    1. Keep all applications in the same module, and then use code-splitting
>    to ensure only necessary code gets downloaded
>    2. Maintain separate modules for each app, plus a common module that
>    every app reuses.
>
> Both have advantages and disadvantages, and you should make a decision based
> on your exact needs.
>
> *Code Splitting*
>
>    - Shared code is only downloaded once
>    - Requires your application to be shipped in one app. No way to create
>    multiple war files.
>    - Since you only have a single module, you have tight coupling between
>    the apps.
>
> *Multiple Modules*
>
>    1. Shared code will be included with every application, and hence
>    downloaded multiple times. But portions of the shared code that are unused
>    will not be included with the application.
>    2. Shared code is reused as jar files prior to compilation. After
>    compilation, every app is self contained.
>    3. The applications can be separate war files, no runtime coupling at
>    all.
>
> What would be a good architecture?
>
> If the user is likely to visit two apps in the same browsing session, use
> code splitting. Otherwise go for multiple modules.
>
> --Sri
>
> On 2 June 2010 12:56, Erik van Ingen <[email protected]> wrote:
>
> > Let's say that I have about 5 different applications in my website.
> > All these application do share GWT components. A  visitor may use 1 or
> > more applications.
>
> > Given this usecase, I have a few questions:
> > (1) Is is possible in GWT to isolate these shared GWT components in
> > such a way that they are not loaded twice in the browser when a
> > visitor is using 2 applications? If yes, how?
> > (2) Do the 5 applications need to be shipped in 1 webapp?
> > (3) Would it be possible to ship the shared components in a different
> > webapp?
> > (4) What would be a good architecture, given the usecase?
>
> > --
> > 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]<google-web-toolkit%[email protected]>
> > .
> > 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 [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.

Reply via email to