It all depends on how productive YOU and your organization will be with any given set of technologies. C is archaic, as is CGI, but they still "work". Some things you should know about CGI, though:
http://en.wikipedia.org/wiki/Common_Gateway_Interface#Drawbacks The only reason I would see for going the C/CGI route is if everyone in the organization already knows C/CGI, you have existing software built in C (or any other language) that you don't want to write a web- based layer around, or you're a glutton for punishment :) On Sep 22, 3:55 pm, Falcon <[email protected]> wrote: > I'm not sure why you'd want to when there's PHP, Perl, Python, Ruby, > Java, etc. Unless there's some special reason to use C that I don't > know about you'll probably be a lot more productive using a higher > level language. > > The GWT forum is kind of a strange place for this question. Java is > certainly the easiest to use on the server with GWT, but technically > you should be able to use any language on your server with GWT as long > as you can communicate via one of JSON, XML, etc. > > On Sep 21, 8:24 pm, Michael <[email protected]> wrote: > > > > > Given PHP, and all the other alternatives is C / CGI still a > > reasonable way to go? -- 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.
