Hi, Just my opinion, so take my strong statements with a grain of salt as I have a tendency to see my problems as being the most important in the world :-) But you were asking for input, right ?
GWT is being pushed as THE tool for AJAX development. The RPC part is fundamental to the AJAX experience yet it does not scale very well beyond a Hello World or Twitter client. And for the Twitter client one could argue that you really need a standard implementation for push messaging instead. RPC is really bad with object graphs. If you have a tree or linked list you don't need a lot of nodes to see it crash with a stack overflow. Sending larger payloads is also the best way to make the app stall. The current RPC is just fundamentally broken in the implementation that maybe it does not deserve to be in GWT 2.0 either. I do not see any need to move my code to GWT 2.0 if the RPC is not fixed. The new UI features are nice to have but not critical to the applications. The JS optimisations do not make a lot of difference since our UI's are not really CPU bound. The new widgets or declartive UI part is nice, but we can do without - a faster table/tree implementation in the trunk would be very usefull (the incubator seems to be dead ?) since it is the main reason why people select ExtGWT or other GWT widget sets (which do not really use GWT the way they should). The only thing that is really missing in GWT is a decent RPC that can be trusted to just work. David On Mon, Oct 19, 2009 at 9:49 PM, Bruce Johnson <[email protected]> wrote: > So, here's the deal on deRPC. It doesn't yet have the miles on it that we'd > like, so we're pretty much on the fence as to whether to really ship it in > GWT 2.0 or not. > It has been included in MS1 and will be in MS2, but we may still make a "no > go" decision before the GWT 2.0 RC comes out. > If you (as in, anyone reading this email) have tried the new RPC stuff and > have feedback, now would be the right time to give it a thumbs up or thumbs > down. At the moment, we're leaning thumbs down -- mainly to be conservative. > -- Bruce > On Mon, Oct 19, 2009 at 3:45 PM, Sami Jaber <[email protected]> wrote: >> >> Following a question I asked privately to Bruce and Amit. >> Thanks for your response gwitters >> >> Sami >> >> On Mon, Oct 19, 2009 at 9:38 PM, Bruce Johnson <[email protected]> wrote: >>> >>> Sami, would you mind asking this question directly on the Contributors >>> list? We can answer it so that everyone has a chance to comment. >>> Thanks. >>> >>>>> >>>>> On Sat, Oct 17, 2009 at 1:46 AM, Sami Jaber <[email protected]> >>>>> wrote: >>>>>> >>>>>> Bruce, >>>>>> >>>>>> What is the status of deRPC API in GWT 2. The code is in the trunk, it >>>>>> seems to be work very well (at least with my test cases) but nothing in >>>>>> GWT >>>>>> MS1 Amit announce and very few gwtc posts regarding the API/issue. >>>>>> Are you planning to ship deRPC with GWT 2 (I would love to regarding >>>>>> all the JDO/AppEngine integration) ? Similarly, are you planning to >>>>>> update >>>>>> GPE to conform to the new interfaces, RpcService, RpcServlet, etc ... >>>>>> (http://code.google.com/eclipse/docs/gwt_rpc.html) ? >>>>>> >>>>>> Thanks for you response, >>>>>> >>>>>> Sami >>>>>> >>> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
