Re: [gwt-contrib] Deprecating DeRPC classes
Hi Stephan, Could you please let me know is there any patch available to check the impact of removing de rpc calls. Thanks in advance.. Have a good day. Regards, Naresh Yakkala. On Thursday, 20 September 2012 20:18:39 UTC+5:30, Stephen Haberman wrote: Or should I go ahead and propose a patch that deprecates it or even removes it? That seems like a great idea to me; I would say go ahead and submit a patch to remove it. I suppose it is inevitable that some internal Google projects still use it, but it would be nice to at least know, and I think Ray/Brian submitting a patch and letting their build system figure it out what breaks is the quickest way to know. If anything we can queue it up for the eventual non-google trunk where hopefully we have a bit more freedom with this sort of stuff. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
Hi Naresh, Could you please let me know is there any patch available to check the impact of removing de rpc calls. I'm glad you're interested in looking in to this. Unfortunately, I don't really know much about DeRPC. There are probably others on the gwt-contrib list who do though...we'll see if anyone can point you in the right direction. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
The first step would be to delete com.google.gwt.rpc and the HybridServiceServlet, and then remove all the hooks in RPC that were added to make deRPC possible (there's at least one in RemoteServiceServlet), and probably others in the RPC generator. On Tuesday, November 5, 2013 5:26:21 PM UTC+1, Stephen Haberman wrote: Hi Naresh, Could you please let me know is there any patch available to check the impact of removing de rpc calls. I'm glad you're interested in looking in to this. Unfortunately, I don't really know much about DeRPC. There are probably others on the gwt-contrib list who do though...we'll see if anyone can point you in the right direction. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
Just curious, is there a particular impetus to removing DeRPC at this time? E.g., is it causing code bloat or slowness, or making new development more difficult? I'm fine with marking the class as @Deprecated, but unfortunately we [Google] still have an internal customer using DeRPC and so far I haven't been successful in convincing them to prioritize moving off of it. (I did manage to remove our other internal uses of DeRPC.) Alternatively, if there's an easy way for us to split DeRPC out of GWT core and maintain it separately, I'm happy to do that (e.g., we're already doing that for GWTShell). But it sounds like DeRPC is heavily entangled into GWT-RPC? On Tue, Nov 5, 2013 at 9:45 AM, Thomas Broyer t.bro...@gmail.com wrote: The first step would be to delete com.google.gwt.rpc and the HybridServiceServlet, and then remove all the hooks in RPC that were added to make deRPC possible (there's at least one in RemoteServiceServlet), and probably others in the RPC generator. On Tuesday, November 5, 2013 5:26:21 PM UTC+1, Stephen Haberman wrote: Hi Naresh, Could you please let me know is there any patch available to check the impact of removing de rpc calls. I'm glad you're interested in looking in to this. Unfortunately, I don't really know much about DeRPC. There are probably others on the gwt-contrib list who do though...we'll see if anyone can point you in the right direction. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
DeRPC was essentially an experiment that didn't work out, it was supposed to improve the speed of IE6. It added a lot of hacks to the compiler to make it work, @ArtificialRescue, ability to invoke client-side methods from server emitted functions, which actually requires clever hacks in some classes to prevent inlining (see java/lang/Class emulation code) It would be good to remove it. If you want really fast RPC, go with something like JAXRS + JSOs. Parsing is blistering fast with JSON.parse() on today's browsers, and there's no need to deserialize/copy. RestyGWT is one possibility. On Tue, Nov 5, 2013 at 10:07 AM, Matthew Dempsky mdemp...@google.comwrote: Just curious, is there a particular impetus to removing DeRPC at this time? E.g., is it causing code bloat or slowness, or making new development more difficult? I'm fine with marking the class as @Deprecated, but unfortunately we [Google] still have an internal customer using DeRPC and so far I haven't been successful in convincing them to prioritize moving off of it. (I did manage to remove our other internal uses of DeRPC.) Alternatively, if there's an easy way for us to split DeRPC out of GWT core and maintain it separately, I'm happy to do that (e.g., we're already doing that for GWTShell). But it sounds like DeRPC is heavily entangled into GWT-RPC? On Tue, Nov 5, 2013 at 9:45 AM, Thomas Broyer t.bro...@gmail.com wrote: The first step would be to delete com.google.gwt.rpc and the HybridServiceServlet, and then remove all the hooks in RPC that were added to make deRPC possible (there's at least one in RemoteServiceServlet), and probably others in the RPC generator. On Tuesday, November 5, 2013 5:26:21 PM UTC+1, Stephen Haberman wrote: Hi Naresh, Could you please let me know is there any patch available to check the impact of removing de rpc calls. I'm glad you're interested in looking in to this. Unfortunately, I don't really know much about DeRPC. There are probably others on the gwt-contrib list who do though...we'll see if anyone can point you in the right direction. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
Sorry, let me clarify: I know what DeRPC is and why we'd want to get rid of it. I'm asking why we're discussing getting rid of it *now*. Like I said, Google has an internal user for it still, so someone (most likely me) would need to invest time in helping them transition off before we can delete it. I want to make sure that effort is well spent. On Tue, Nov 5, 2013 at 5:00 PM, Ray Cromwell cromwell...@google.com wrote: DeRPC was essentially an experiment that didn't work out, it was supposed to improve the speed of IE6. It added a lot of hacks to the compiler to make it work, @ArtificialRescue, ability to invoke client-side methods from server emitted functions, which actually requires clever hacks in some classes to prevent inlining (see java/lang/Class emulation code) It would be good to remove it. If you want really fast RPC, go with something like JAXRS + JSOs. Parsing is blistering fast with JSON.parse() on today's browsers, and there's no need to deserialize/copy. RestyGWT is one possibility. On Tue, Nov 5, 2013 at 10:07 AM, Matthew Dempsky mdemp...@google.comwrote: Just curious, is there a particular impetus to removing DeRPC at this time? E.g., is it causing code bloat or slowness, or making new development more difficult? I'm fine with marking the class as @Deprecated, but unfortunately we [Google] still have an internal customer using DeRPC and so far I haven't been successful in convincing them to prioritize moving off of it. (I did manage to remove our other internal uses of DeRPC.) Alternatively, if there's an easy way for us to split DeRPC out of GWT core and maintain it separately, I'm happy to do that (e.g., we're already doing that for GWTShell). But it sounds like DeRPC is heavily entangled into GWT-RPC? On Tue, Nov 5, 2013 at 9:45 AM, Thomas Broyer t.bro...@gmail.com wrote: The first step would be to delete com.google.gwt.rpc and the HybridServiceServlet, and then remove all the hooks in RPC that were added to make deRPC possible (there's at least one in RemoteServiceServlet), and probably others in the RPC generator. On Tuesday, November 5, 2013 5:26:21 PM UTC+1, Stephen Haberman wrote: Hi Naresh, Could you please let me know is there any patch available to check the impact of removing de rpc calls. I'm glad you're interested in looking in to this. Unfortunately, I don't really know much about DeRPC. There are probably others on the gwt-contrib list who do though...we'll see if anyone can point you in the right direction. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
Is DeRPC actually in use somewhere? Or should I go ahead and propose a patch that deprecates it or even removes it? -Daniel 2012/9/11 Chris Lercher cl_for_mail...@gmx.net https://developers.google.com/web-toolkit/doc/latest/DevGuideServerCommunication#DevGuideDeRPC says about Direct-Eval RPC: This feature did not work out as planned, and the GWT team strongly discourages its use. However, the classes RpcServlet, RpcService etc. are not marked as deprecated. It's easy to mistype RemoteService as RpcService, which doesn't cause any warning. If this happens, it can be very difficult to spot the problem, and it's not trivial to revert to RemoteService, see for example: http://code.google.com/p/google-web-toolkit/source/diff?spec=svn11258r=11229format=sidepath=/trunk/samples/validation/src/main/java/com/google/gwt/sample/validation/client/GreetingService.javaold_path=/trunk/samples/validation/src/main/java/com/google/gwt/sample/validation/client/GreetingService.javaold=10642 -- http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Deprecating DeRPC classes
https://developers.google.com/web-toolkit/doc/latest/DevGuideServerCommunication#DevGuideDeRPC says about Direct-Eval RPC: This feature did not work out as planned, and the GWT team strongly discourages its use. However, the classes RpcServlet, RpcService etc. are not marked as deprecated. It's easy to mistype RemoteService as RpcService, which doesn't cause any warning. If this happens, it can be very difficult to spot the problem, and it's not trivial to revert to RemoteService, see for example: http://code.google.com/p/google-web-toolkit/source/diff?spec=svn11258r=11229format=sidepath=/trunk/samples/validation/src/main/java/com/google/gwt/sample/validation/client/GreetingService.javaold_path=/trunk/samples/validation/src/main/java/com/google/gwt/sample/validation/client/GreetingService.javaold=10642 -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
