Connections should be short-lived, so from an absolute perspective, yes. From a practical perspective, if your requests are designed to execute as quickly as possible, it'll take a long time before this affects application performance. Note that static assets do not count against this limit.
On Thu, Mar 4, 2010 at 10:44 AM, Bobby Sawhney <bobbysawh...@gmail.com> wrote: > On Mar 2, 6:05 am, "Nick Johnson (Google)" <nick.john...@google.com> > wrote: >> Actually, the default limit is 30 active requests. >> >> -Nick Johnson > > Hi Nick, > > Will Google make "simultaneous dynamic requests limit" be part of a > billable option in the future, such that applications can pay to have > this limit increased? > > Also, a question for other developers using GAE with AJAX. Does this > not imply that each client is already using 2 of the connections from > this limit, thus halving the number of concurrent clients able to use > the application? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
