You'd either have to put a proxy infront or serve off two urls, not an ideal use case.
From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Chris Ramsdale Sent: Friday, December 30, 2011 12:58 PM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] Re: Feature Request I Think.... For the use case you provided, why not split the low latency and high latency requests into two different apps (each with specific performance tuning)? -- Chris On Wed, Dec 21, 2011 at 12:10 PM, stevep <prosse...@gmail.com> wrote: Still voting for task queue optimization. Hopefully we get TQ access in the /api app. Example, if I get a huge burst of traffic, for certain types of recs I would much rather build a queue backlog rather than spin up new 10s latency instances. TQFTW. stevep. On Nov 29, 11:36 am, Chris Ramsdale <cramsd...@google.com> wrote: > Great feedback. Here's the model that I've been envisioning: > > - I have foo.com and foo.com/api > - foo.com serves up my UI and needs to be super-fast > - foo.com/api serves up non-realtime API requests > - both route to a separate App Engine app > - foo.com has max pending latency of 200ms, and several idle instances > - foo.com/api has a max pending latency of 10s > - Each app is part of a larger "system" that is configurable within the > Admin Console > - Being part of a larger "system" sets up the correct ACLs between apps and > services (e.g. each app is able talk to the same Datastore) > > A couple of notes: > - There needs to be a simple way of routing requests. Routing foo.com to > the "system", and configuring paths that map to apps (e.g. /api routes to > api.foo.appspot.com under the covers is one suggestion) > - Configurable Memcache that can be shared by each app would be nice, still > iterating on this one > - Expose a few more Backend properties to Frontends, and one could imagine > Backends and Frontends merging under this model > - Is there "system" billing and per-app billing? > > -- Chris > > On Fri, Nov 25, 2011 at 7:26 AM, Jamie Nelson <jamie.nel...@promevo.com>wrote: > > > > > > > > > How about a header we can append to have a request routed to a > > particular instance-class? > > > For those of us using gwt, appending an @Instance(target="a1") or > > @Latency(expected=2500) annotation to rpc methods could append the > > appropriate header to route requests based on their expected latency. > > > This would be faster for all of us, and easier on your servers. > > > If this feature is released, I will personally write the generator > > patch to implement the annotation {as opposed to have RpcAsync methods > > return RequestBuilder to manually set each request}. > > > On Nov 25, 7:01 am, Joshua Smith <joshuaesm...@charter.net> wrote: > > > On Nov 24, 2011, at 12:06 PM, stevep wrote: > > > > > Seeing the > > > > many new names from Google in the forums, I'm assuming that is the > > > > case. > > > > I noticed this, too. Can anyone from google comment (just between us > > girls), is GAE getting some traction inside the googleplex now that you're > > out of preview? Do you get mentioned in high-level meetings? Are you > > getting some more budget to work with? Are new insanely smart people > > looking to get into your group? Is Brandon's mermaid costume discussed at > > every water cooler? > > > > -Joshua > > > -- > > 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-appengine@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine+unsubscr...@googlegroups.com <mailto:google-appengine%2bunsubscr...@googlegroups.com> . > > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com <mailto:google-appengine%2bunsubscr...@googlegroups.com> . 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 google-appengine@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. -- 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-appengine@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.
