GWT is going non-monolithic (runAsync)
There have been many discussions on GWT forums about the monolithic nature of javascript produced by GWT’s java-to-javascript compiler (typical GWT compilation output consists of a single .js file produced for every major browser). Although this certainly is a tried-and-true approach in GWT for improving performance, many developers of large GWT-based projects would like to have the flexibility to partition their applications and load their parts dynamically at runtime. It looks like Google WebToolkit team is making great progress in implementing this exact functionality in a future release. I noticed this branch (called runAsync) within GWT trunk. And here is sneak peak at how it may look like in the code:
AsyncCallback<MyBigCompositeWidet> callback= new AsyncCallback<MyBigCompositeWidet>() {
public void onFailure(Throwable caught) {
// TODO Auto-generated method stub
}
public void onSuccess(MyBigCompositeWidet result) {
result.setVisible(false);
}
};
GWT.createAsync(MyBigCompositeWidet.class, callback)
Pretty Slick!
No related posts.
Hi there,
This is exactly what we need in GWT! I’m googling hard but can’t find any more info for this, do you know have any details on when this will be part of the official release? 1.6? Our web app will rely on it!
David
You don’t actually show any code with runAsync in it though. The example you give is just a traditional RPC call.