Hi lineman, a real good GUI very soon needs to update from server side will appear. Either COMET or if possible HTML5 Websocket will be necessary. I do not see REST in this scenario.
>From the architectural point of I would never access web services directly, too. web services are blind to the special needs of a GUI. There is an impedance mismatch (similar to relational database and object orientation) So a layer in between gives you the place to adapt web services to gui needs. The natural choice is GWT-RPC, however, REST may work, too. In the extra layer you may do (when useful): a) caching service results b) accessing services needing credentials not known by the user. The extra layer may improve performance and latency when used adequat. Stefan Bachert http://gwtworld.de PS: I never argue with obscurity regarding security, meaning I agree with you, it is a poor idea for security > One last point... Even though GWT-RPC has some small advantages over > REST because it is based on REST, it is by far not the best solution > for large projects. The main purpose of using REST is that it is > platform independent as far as the client goes. With GWT-RPC only GWT > can be used, but with REST anything can consume it, especially when > you expose several different output media types like I do. For my > services a client can request that I send the response back in 4 > different forms: XML, JSON, JSONP and Java Serialization. This is > very important because possible consumers of our services include > Java, JS, C++ and C# clients. We could argue all day on which > implementation is better and it truly comes down to the fact that it > depends on the requirements of the project. For work projects I tend > to use REST; for personal I use GWT-RPC because I know the client will > always be GWT. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
