> With browsers becoming more aware and supporting sources from multiple > sources, SOP is not so much an issue.
first of all SOP is a browser topic not an GWT. I don't think that browsers will give up security. > That is a sad state of affairs and ties the client to a GWT-RPC > speaking backend. It is probably the most secure approach. You can switch to JSON(P) if security is not important. > > I know many people are impressed by the flexibility and power of GWT > as a client side technology (especially on html5 enabled mobile > devices!!!), but would like to use alternative tools on the server > (eg: rails). Proper REST support would really ease the way for > developers to create cleanly separated clients using GWT and backends > using whatever RESTful tools they want. What is the problem to call them from GWT-serverside ? (By the way, Spring Roo may become a substitute for rails when fully supporting GWT) To mashup to any service from browser looks only attractive at the first glance. It would be a security disaster. No browser vendor will allow this. Stefan Bachert http://gwtworld.de -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
