But you still can't serve > 1 request at a time. So the single-thread restriction is very relevant.
On Fri, May 13, 2011 at 5:08 PM, Robert Smart < [email protected]> wrote: > If you look at the go docs it looks like it only supports sync ops on > urlfetch/datastore/etc. However when one of these ops is started then other > goroutines start running. And the goroutines can send messages to each > other. So go provides the only language-native async system for gae. Rob > Pike claims that this is a good way to think about async operations. There > isn't much CPU involved usually, so the restriction to 1 thread is really > irrelevant most of the time. > > However you'd need to be very brave to go for go when we haven't even seen > a draft of how they plan to do transactions and channels. Or have we? > > -- > 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.
