-
Get a monthly update on best practices for delivering successful software.
Joel tackled a tough subject, IMHO. Talking about architecture in the absence of a concrete application that you want to convert to GWT (and that's what most of the folks here are looking to do), you end up giving fairly general prescriptions and best practices. The areas of focus were:
Billy Hoffman called Joel out on the state to the client stuff and the security holes it opens. The response: be careful what state you put on the client, but much of the session state doesn't really need to be in the session. Given the audience response that followed, I think Billy can start printing money.
All in all, it seems that best practices for GWT applications are still evolving.
Some more Joel quotes:
"We used to call this DHTML, but it has a fancy new name, so we call it Ajax."
"Apparently no one can agree on what a controller is and will argue all day. What's important is that you have a model and a view and those are distinct."
"Once you understand that data updates are asynchronous, you start to think about your application in a different way, that you will get events and data updates in an unpredictable order. You just have to draw out what all the possible states have to be."
"When you move all of your session state into the client, it is usually possible to have essentially stateless servers. A stateless server gives you free scalability. However I can't help you with your database."
Related posts:
Topics: Best Practices, GWT
Hello, everyone is interested in printable and readable version of this conference Coogle IO, please look
http://extgwt-mvp4g-gae.blogspot.com/2009/10/gwt-app-architecture-best-practices.html
Comment by Araminos, Thursday, October 22, 2009 @ 8:47 pm