For the time being that is indeed true. We are working on ways to bring concurrency to Python but don't have anything we can announce just yet. Go is currently single-threaded, but this too is something that could change over time.
Greg On Tue, May 10, 2011 at 12:10 PM, Ugorji <[email protected]> wrote: > Hi Greg, > > Thanks much for the response. I understand responses will be slow this > week. > > For once, it now seems that Java has an advantage, as Python (and GO) users > do not have the option of using multi-threaded to reduce the number of > instances. So although Python (and GO) will *potentially use less resources > and a lower footprint, will they now get charged more due to a limitation in > the app engine runtime? > > I've been developing with Java, but am pretty excited about GO's inclusion. > This seems to be a bottleneck. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine?hl=en.
