It sounds like much of your performance is issues will probably be more database related than anything, so a lot of the other backend decision probably come down to personal preference or experience.
I've been working on a GWT project that talks to a Django/MySQL backend for several months. The RPC is all JSON, which requires a bit of marshalling logic on each end, but so far it's not been a maintenance problem (the data model is fairly stable). If you're worried about Python's GIL for concurrent web requests, I don't think that's an issue because you're going to be running different instances of the runtime (each with their own GIL) for parallel web requests. Apart from a personal preference for Python's syntactic economy, I found I could get my head around Django's ORM, session management and other back-end functionality very quickly. Not wanting to rebuild all of this (or relearn in a new framework) is primarily what drove the Django selection. The Java servlet path may just be suffering from a wealth of options, but it felt like a lot more mental effort to put the appropriate platform together. Which probably just means I'm lazy. It's the devil you know... I'm sure somebody with more depth of experience on the various Java server side frameworks would come to different conclusions. As rjcarr points out, GWT-RPC makes a compelling case for going that route especially with the tools evolving more and more. The downsides you've pointed out are definitely there... You're switching between languages all day (forgetting semicolons in Java and putting extraneous ones into the Python), and you catch a lot more runtime issues that a strongly-typed language would have been caught at compile time, but still nothing FireBug and Django's debug responses don't highlight well. -- 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.
