I've seen the same behavior. All the classes passed via RPC get pulled in when initializing the RPC serialization. This will get kind of ugly for our app when it gets larger as we use the command pattern for RPC and it will pull in a lot of code at startup.
On May 13, 12:59 pm, brianw <[email protected]> wrote: > hi there, > > I've been experimenting with code splitting to reduce the size of the > initial load. > Parts of the login page, which is the first page calling up the > application - is stored > in the database. this requires, ofcourse, an rpc call to the server. > it seems that this call forces the inclusion of all other code which > makes use of any rpc. > I say this because the dependency chains of the loaded classes all > start at this first call, continue with the gwt classes, and then > continue with the rpc call of that class. > > I was wondering if this is expected behaviour and if so, then, is > there any way around > without eliminating the first call. > > thank you for any assistance that you might be able to provide > B > > -- > 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 > athttp://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.
