tag:blogger.com,1999:blog-1647878561657161390.post3089080458033760595..comments2023-11-03T08:05:08.639-04:00Comments on GoGoCarl: The Internet: An Alternative to GWT's RPCCarl Scotthttp://www.blogger.com/profile/02372135317795354157noreply@blogger.comBlogger13125tag:blogger.com,1999:blog-1647878561657161390.post-3290831732076722582010-04-23T11:47:32.252-04:002010-04-23T11:47:32.252-04:00Giving relative numbers doesn't really help to...Giving relative numbers doesn't really help to assess the exact size added by Restlet to a GWT application.<br /><br />We have just released <a href="http://blog.noelios.com/2010/04/23/restlet-framework-2-0-rc3-released/" rel="nofollow">version 2.0 RC3</a>, including a size optimization for the GWT edition. <br /><br />We kept only the most often used MediaType constants, saving 6 Kb. This results in an absolute size of 159 Kb that can be GZipped down to 65 Kb, far from the nightmare you announce.<br /><br />Regarding the "spaghetti dish", could you elaborate a bit more? <br /><br />On our side, we are planning further optimizations. Our org.restlet.client.representation.ObjectRepresentation class depends on the GWT-RPC module for object serialization. We will move it to a separate extension, making GWT-RPC optional, further reducing the core size.<br /><br />In Restlet 2.1, we will also add an option to our <a href="http://wiki.restlet.org/docs_2.0/13-restlet/21-restlet/318-restlet/303-restlet.html" rel="nofollow">client proxies generated via deferred binding</a> to make them only rely on GWT's HTTP+RPC modules internally, saving the Restlet module size if no further inspection/modification of HTTP messages is needed at runtime.<br /><br />In the end, you should only increase your application size for the feature you really use/need. That's our goal.Jerome Louvelhttps://www.blogger.com/profile/11420230422390280351noreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-58341140701756310312010-04-15T05:27:43.614-04:002010-04-15T05:27:43.614-04:00Just don't use Restlet's GWT edition, it m...Just don't use Restlet's GWT edition, it made my GWT app like 30% bigger. It's a huge spaghetti dish, all units intercoupled, lot's of hardcoded data (mime types). I found it much easier and efficient to use GWT's overlay types + it's HTTP client API + gwt-dispatch (http://code.google.com/p/gwt-dispatch/). It's build for RPC but it can be used with REST as well after custom service impl.skrathttps://www.blogger.com/profile/15487467627010327242noreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-56127353901387216712009-11-16T13:30:05.711-05:002009-11-16T13:30:05.711-05:00Hmm, could be an interesting framework as we begin...Hmm, could be an interesting framework as we begin to use JSON more. Will certainly keep this in mind, thanks for the recommendation!Carl Scotthttps://www.blogger.com/profile/02372135317795354157noreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-46946629560476741972009-11-16T09:52:32.407-05:002009-11-16T09:52:32.407-05:00If you guys are looking for a resful aproach to do...If you guys are looking for a resful aproach to doing GWT based RPC, then take a peek at the <a href="http://github.com/chirino/resty-gwt" rel="nofollow">RestyGWT</a> project. RestyGWT is a GWT generator for REST services and JSON encoded data transfer objects.Hiram Chirinohttps://www.blogger.com/profile/16983993595849131879noreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-76390778910585294932009-11-13T06:58:17.040-05:002009-11-13T06:58:17.040-05:00Who knows where to download XRumer 5.0 Palladium? ...Who knows where to download XRumer 5.0 Palladium? <br />Help, please. All recommend this program to effectively advertise on the Internet, this is the best program!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-83271603432406612302008-07-25T09:42:00.000-04:002008-07-25T09:42:00.000-04:00Impeccable timing, I just heard the news and did s...Impeccable timing, I just heard the news and did some reading up on it and some other REST technologies:<BR/>http://gogocarl.blogspot.com/2008/07/restful-client-side-tools-for-gwt.html<BR/><BR/>Thanks for the time in reading, much appreciated!Carl Scotthttps://www.blogger.com/profile/02372135317795354157noreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-60019380785957332032008-07-25T09:09:00.000-04:002008-07-25T09:09:00.000-04:00Hi Carl,Thanks for the nice post and comments! We ...Hi Carl,<BR/><BR/>Thanks for the nice post and comments! We have great news on the Restlet + GWT front... :-)<BR/><BR/>With the help of Rob Heittman, your CTO at Solertium, we have just <A HREF="http://blog.noelios.com/2008/07/25/restlet-ported-to-gwt/" REL="nofollow">released a port of Restlet to GWT</A>.<BR/><BR/>Best regards,<BR/>JeromeJerome Louvelhttps://www.blogger.com/profile/11420230422390280351noreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-8917887151657930072008-07-10T02:24:00.000-04:002008-07-10T02:24:00.000-04:00Thanks for the read and recommendation! I actuall...Thanks for the read and recommendation! I actually do not personally use GWT REST, though I have delved into its code and spoke with the developers. It seems usable, but it also looks like there a bit of unnecessary bloat in there for most applications. If you've got a good grasp of REST principles and you plan on reeeally utilizing its full functionality, try it out. Once I get client-side, though, I don't find myself in need of a REST wrapper. But again, the more you utilize more advanced functionality, the more it seems to be useful, but I have not personally used it.<BR/><BR/>I must say, I'm a fan of RestLet, but I'll given Jersey a look too -- thanks again!Carl Scotthttps://www.blogger.com/profile/02372135317795354157noreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-38482765724075025872008-07-08T03:57:00.000-04:002008-07-08T03:57:00.000-04:00Hi, nice article.Do you use GWT-REST? Would you re...Hi, nice article.<BR/><BR/>Do you use GWT-REST? Would you recommend it?<BR/><BR/>As an alternative to RestLets, I've been using Jersey, and like it so far.<BR/>If you assemble your resource with JAXB, it is just a question of a single annotation to produce JSON or traditional XML representation.Szocskehttps://www.blogger.com/profile/12599113790801100227noreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-25242154063108488262008-05-05T13:29:00.000-04:002008-05-05T13:29:00.000-04:00Valid points, and yes I think that a proxy generat...Valid points, and yes I think that a proxy generator is a good ways away if it's even being considered by the dev team. Really, the whole idea behind the implementation though it to decouple the unnecessary relationship between GWT client and server. You have a RESTful, independent client running and GWT just makes calls to the server.<BR/><BR/>I'll be doing another blog soon with more details on this, so check back soon. Thanks for the read!Carl Scotthttps://www.blogger.com/profile/02372135317795354157noreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-91898520659618586592008-05-05T04:35:00.000-04:002008-05-05T04:35:00.000-04:00Hi Carl,we are VERY interested in reading more abo...Hi Carl,<BR/>we are VERY interested in reading more about RestLet and GWT.<BR/><BR/>I think that a problem the GWT community currently has is generating intelligent stress-tests for their GWT applications.<BR/><BR/>You just can't affort to run a firefox image for each user you want to simulate, and on the other hand you can't just playback pre-recorded RPC calls because you want to generate requests according to your own criteria and logical sequence...<BR/><BR/>The best solution for us would be a proxy-generator creating for us a pure java proxy from the GWT service specification: this way a java application might easily generate all the RPC calls by simply invoking the proxy methods.<BR/><BR/>Unfortunately, after a short survey , it seems that such a proxy generator does not exist.<BR/><BR/>So this is where our interest in RestLet comes for: maybe we can "open up" our GWT backend so that it can be used by both the GWT (JS) client running in the broswer AND by any other authorized application (including our java stress test).<BR/><BR/>Could you please provide more info in GWT / RestLet ? Thanks.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-70738734655474552762008-04-30T13:12:00.000-04:002008-04-30T13:12:00.000-04:00Oh I agree, within the context of GWT where there ...Oh I agree, within the context of GWT where there is a known intermediary, you can have your server return XML representations for GWT to do interesting things with.<BR/><BR/>RestLet's Resource implementation utilizes Variants, which you can use to change the representation based on what you want, so you can return HTML, XML, etc. representations of the same resource based on the request. This comes in handy when you'd want XML reps for GWT, but, in the case you pointed out, be able to have a readable rep outside that context.Carl Scotthttps://www.blogger.com/profile/02372135317795354157noreply@blogger.comtag:blogger.com,1999:blog-1647878561657161390.post-17950183432810839782008-04-29T16:08:00.000-04:002008-04-29T16:08:00.000-04:00I reed your article and i agree with you that RPC ...I reed your article and i agree with you that RPC programming in GWT is somehow laborious. In my experience, the big problem of AJAX is the "X" which represents XML. It is easy to read by human beings but it es very expensive to read for browsers (in terms of cpu load and memory). <BR/><BR/>So, whatever you want to optimize with a REST . Please keep in mind not to transfer XML object representations. Transmit something that is easy to read BY BROWSERS without additional plug-ins or special xml libraries. Otherwise, you can make better results by using other client GUIs. GWT is made and opimized for the standard web client (the browser).Anonymousnoreply@blogger.com