Are there any wiki pages or other docs explaining the deRPC approach that one can read? Or maybe a list of major classes one could take a look at?
Specifically, I'm interested in the "much more hackable code base" mentioned in this post: http://groups.google.com/group/google-web-toolkit-contributors/browse_thread/thread/631b8c3177930913/6f15dbd5243f10b3 Thanks, Yegor On Oct 19, 2:28 pm, Bruce Johnson <br...@google.com> wrote: > Love the enthusiasm! > Anyone else? > > On Mon, Oct 19, 2009 at 4:26 PM, Sami Jaber <sami.ja...@gmail.com> wrote: > > IMHO, It would be a mistake not to make it happen for GWT 2 > > > deRPC is a huge step forward in terms of performance, extensibility, > > command sinking, serialization extensibility, security and so forth > > Everybody know that GWT 2 will introduce new API and many new > > functionalities, why deRPC would not be part of the show? > > Because it has not been intensively tested ? There's probably a lack of > > tests cases, sure, but it is not specific to deRPC. When I see the last > > commit streams, deRPC seems to me more reliable than other APIs. And > > regarding the migration path and the different use case scenarios, this is > > sweet. If you want to stay in legacy land, just use the straight > > RemoteServiceServlet class. If you want to support the two modes, just > > inherits from HybridServiceServlet (as JUnitHostImpl does in the trunk right > > now). If you are a newcomer, forget all the old non-extensible interfaces > > and use RpcServlet and RpcService. > > > Releasing deRPC does not mean that you won't be able to patch if later. > > Earlier it will be released, earlier you will get feedback. Please think > > about it. > > > My 2 french euros, > > > Sami > > > On Mon, Oct 19, 2009 at 9:49 PM, Bruce Johnson <br...@google.com> 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 <sami.ja...@gmail.com> 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 <br...@google.com> 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 > >>>>>> <sami.ja...@gmail.com>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 -~----------~----~----~----~------~----~------~--~---
