Hi, I am working on a database driven GWT application. Now, in my client side I make RPC calls to basically fetch information from the databse. But the problem is that my client side code gets cluttered with RPC calls and onFailure methods and onSuccess methods. Along with this my UI code is also getting mixed up.
I would like to put all my RPC calling logic in some sort of a delegate class and let the delegate class return the values to my Client class. But I doubt if that will work out as the return type of the onSuccess method is void :( Is there a way to avoid this ? To summerize, this is what I would like to have : Client (Design Layout, Call delegate method) ----------------> Delegate (make RPC calls, return value to Client) -------------> Server (Implement DAO logic, return value to delegate) Could you please suggest a suitable design pattern for GWT design pattern so that the application can be maintained with ease in future? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
