On Mon, Mar 14, 2011 at 12:37 PM, Ray Ryan <[email protected]> wrote: > [[email protected]] > > What dependency? DI is a pattern, not a commitment to a particular > framework. That said, I agree that taking AsyncProvider from Gin is a bit > presumptuous. I meant to include the gin community on this patch, adding > them now. > > What do you think, folks? The goal here is to sever the dependency > between com.google.gwt.inject.client and GWT RPC. >
To me, the new AsyncCallback is just a more flexible version of the old one, and AsyncProvider seems a generally useful GWT analog to j.u.c.Future and not tied to GIN at all. Besides GWT already has DI built-in -- you can think of GWT.create as DI, since you substitute an implementation based on your module files, but you also can have generators write the implementation on the fly as well. Of course, it is highly GWT-specific. -- John A. Tamplin Software Engineer (GWT), Google -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
