On May 11, 9:57 am, Geoffrey Spear <[email protected]> wrote: > For Python applications, yes, a single request takes up all of the > resources of an instance for the time it's being handled. Java > instances with threading enabled can handle multiple requests.
Fundamentally (although the clothes are still in the wash, not on the line) the old cpu-based resource charge was fair. Unless something drastic changes, the new instance charge model appears heavily, very heavily prejudiced against Python. Egregious in the extreme. Making a decision so unfavorable to one group is weird. Likely so weird that GAE should stop with justifications. Maybe it all works out, but this looks just so weird, so very weird to me. Why punish Python developers?? Cheers, stevep -- 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.
