This infrastructure is for rpc only..seems like most of it can be applied for non-rpc Requestbuilder application

[GoogleCodeExporter]

Can you seperate the server side infrastructure to run on client side for 
non-gwt-rpc applicaitons. It seems like the dispatch infrastructure with 
AsyncCallback with generics should be leveraged with requestbuider with 
REquest Response objects, however same library can be generalized with 
compile options by creating services, dispatch and actions on the client 
side.

An idea is to take the entire dispatch framework and make it work with 
remoteservice/servlets or Requestbuilder interaction as the design doesn't 
need to be hardwired to gwt-rpc only.

I think most of gwt-dispatch can be used besides the servlet binding side, 
which could be polymorphically binded to via gin.

Original issue reported on code.google.com by coderina...@gmail.com on 12 Oct 2009 at 2:22

[GoogleCodeExporter]

I'm always open to making the library more flexible. Will look at this for 2.0. 
Any guidance from people more 
familiar with RequestBuilder would be appreciated.

Original comment by Bitmei...@gmail.com on 28 Apr 2010 at 3:05

• Changed state: Accepted
• Added labels: Milestone-Release2.0

[GoogleCodeExporter]

Original comment by Bitmei...@gmail.com on 18 Aug 2010 at 7:04

• Added labels: Milestone-2.0