The following is a guest post by Zack Grossbart, the creator of the Spiffy UI Framework.
The simple RPC mechanism is GWT’s biggest feature and largest problem. It forms a tight and fragile bond between your client and server. Get either one a little out of sync and nothing works. When it does work GWT-RPC sends indecipherable network data. The solution is REST.
REST is a simple remote procedure call pattern based on standard HTTP. It talks in JSON and gives you a clear division between your client and server. With REST comes simplicity, speed, and accessibility. You can call a REST endpoint from anywhere.
We started Spiffy UI because we wanted an easy way to call REST from GWT without abandoning type safety. REST also let us fix the fragile dependency between out client and server.
Along the way Spiffy UI picked up a comprehensive security framework, reusable CSS templates, and support for mobile platforms. We also packaged it all up in reusable projects that support Maven and Ant. The Spiffy UI project creator can have you up and running with Spiffy UI in under a minute.
Spiffy UI is stable, scalable, simple, and well tested. Tens of thousands of people depend on Spiffy UI applications every day. It came from Novell, the same people who make SUSE Linux, and it’s all open source.
REST makes it work with any server. We have Spiffy UI projects running against Java, PHP, Erlang, and node.js.
Find out more and create your own Spiffy UI project at http://www.spiffyui.org.