Typically, you let Apache front all requests - static as well as dynamic. Apache can be configured to serve static files, and proxy dynamic requests to the backend webserver. That way, you achieve your second objective.
Regarding your first objective - to have multiple GWT modules on a single page. It is possible to define more than one gwt module js files on the same host page -- but that is going to lead to a lot of redundant code in the js files. GWT has been optimized to work as a 'single monolithic compile', and having multiple modules on the same page defeats that. Is there a good reason to have multiple GWT modules? --Sri 2009/9/16 Jayant <[email protected]> > > Hello, > > I have a few gwt modules which work off different webapps. Now I want > to present them on same page. There is also another objective as well. > I have a number of static files, which I would like to serve from a > different server which can server the static files faster rather than > the webapp. > > So I want to put the static files, including the gwt modules and have > the loaded modules communicate with their respective webapps on > different servers. Is this possible directly. Has anyone tried this. > Whats the best way to do this. > > Thanks, > -Jayant. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
